{"id":1179,"date":"2010-07-19T13:44:54","date_gmt":"2010-07-19T17:44:54","guid":{"rendered":"http:\/\/www.webperformanceinc.com\/load_testing\/blog\/?p=1179"},"modified":"2012-02-01T14:36:19","modified_gmt":"2012-02-01T18:36:19","slug":"comparing-to-the-median","status":"publish","type":"post","link":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/2010\/07\/comparing-to-the-median\/","title":{"rendered":"Load Testing Metrics: Comparing to the Median"},"content":{"rendered":"<p>Once you&#8217;ve been using Load Tester for a while, it&#8217;s easy to find the minimum, maximum, and average page durations. But how does that compare against the median page duration, or percentiles?<\/p>\n<p>Starting with Load Tester 3.6, these measurements can now be made, but it&#8217;s been made easier to find in Load Tester 4.1. First, you will need to enable \u201cDetailed Page Durations\u201d. In Load Tester 4.1, simply make sure the \u201cDetailed Page Durations\u201d option is checked on the \u201cData Collection\u201d section of the Load Test Configuration editor.<br \/>\n<img loading=\"lazy\" decoding=\"async\" style=\"cursor: pointer;\" onclick=\"window.open('\/images\/blog\/detailed-page-on-load-config-editor.png', '_blank', 'toolbar=no,width=743,height=355');\" src=\"\/images\/blog\/detailed-page-on-load-config-editor.png\" alt=\"Turning on Detailed Page Duration collection in the Load Configuration Editor\" width=\"572\" height=\"273\" \/><\/p>\n<p>With that setting enabled, just run your Load Test as normal. When examining the Load Test report, use the \u201cSettings\u201d button, and turn on the option to compare the Duration Goal against the Detailed durations. The median is compared to the goal by requiring only 50% of the pages to meet the goal \u2013 other goals can also be specified and analyzed.<br \/>\n<img decoding=\"async\" src=\"\/images\/blog\/detailed-page-report-settings.png\" alt=\"Enabling Detailed Page Durations in the Load Test Report Settings\" \/><\/p>\n<p>Press OK, and the Load Test report will refresh to show you when each selected percentile has exceeded the configured page duration goal. By looking at the report for each page in the testcase, you can quickly get a feel for what percentiles of users were not receiving acceptable performance results.<br \/>\n<img decoding=\"async\" style=\"cursor: pointer;\" onclick=\"window.open('\/images\/blog\/detailed-page-report-table.png', '_blank', 'toolbar=no,width=762,height=781');\" src=\"\/images\/blog\/detailed-page-report-table.png\" alt=\"Load Test Report with Detailed Page Analysis\" height=\"586\" \/><\/p>\n<p>We hope that this feature helps to give you a feel for your performance results. However, our friendly support staff is always willing to answer any questions you may have! Happy Testing!<\/p>\n<p>-Frank<\/p>\n<p>Engineer at Web Performance<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Once you&#8217;ve been using Load Tester for a while, it&#8217;s easy to find the minimum, maximum, and average page durations. But how does that compare against the median page duration, or percentiles?<br \/>\nStarting with Load Tester 3.6, these measurements can now be made, but it&#8217;s been made easier to find in Load Tester 4.1. First, you will need to enable \u201cDetailed Page Durations\u201d. In Load Tester 4.1, simply make sure the \u201cDetailed Page Durations\u201d option is checked on the \u201cData Collection\u201d section of the Load Test Configuration editor.<\/p>\n<p>With that setting enabled, just run your Load Test as normal. When examining the &hellip; <a href=\"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/2010\/07\/comparing-to-the-median\/\">Continue reading &raquo;<\/a><\/p>\n","protected":false},"author":12,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[42],"tags":[17,49],"class_list":["post-1179","post","type-post","status-publish","format-standard","hentry","category-load-tester-software","tag-analysis","tag-load-tester"],"_links":{"self":[{"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/posts\/1179","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/comments?post=1179"}],"version-history":[{"count":24,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/posts\/1179\/revisions"}],"predecessor-version":[{"id":3114,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/posts\/1179\/revisions\/3114"}],"wp:attachment":[{"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/media?parent=1179"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/categories?post=1179"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/tags?post=1179"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}