{"id":50,"date":"2008-10-22T13:36:13","date_gmt":"2008-10-22T17:36:13","guid":{"rendered":"http:\/\/www.webperformanceinc.com\/load_testing\/blog\/?p=50"},"modified":"2008-10-22T13:36:13","modified_gmt":"2008-10-22T17:36:13","slug":"load-tester-improvement-better-success-and-fail-metrics","status":"publish","type":"post","link":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/2008\/10\/load-tester-improvement-better-success-and-fail-metrics\/","title":{"rendered":"Load Tester improvement &#8211; better success and fail metrics"},"content":{"rendered":"<p>Previous versions of Load Tester had 2 metrics describing the success or failure of a web page (or single transaction) during a load test: <em>Repeats<\/em> and <em>Errors<\/em>. A <em>Repeat<\/em> was counted any time a valid HTTP response was received from the server. Errors, however, were a bit more complex. Errors could occur at any point in the transaction, from establishing a connection to post-response validation. An error was counted if the connection was terminated in the middle of a transaction. It was also counted if the status code from the server indicated a failure (e.g. a 500 status). Validators record an error when the expected content was not received from the server. Extractors, which search for dynamic content on a page that is needed later in the testcase, record an error when the required content is not found. This could result in several errors reported for a single web page &#8212; especially since every transaction within a page can generate one or more errors. This made it impossible to determine exactly how many pages were attempted or failed during a given period in a load test.<\/p>\n<p>The 3.6 release of Load Tester will include 4 new metrics, which replace the <em>Repeats<\/em> and <em>Errors<\/em> metrics. The new metrics are <em>Successes<\/em>, <em>Failures<\/em>, <em>Completions<\/em> and <em>Failure Rate<\/em>.<\/p>\n<ul>\n<li>Successes &#8211; A success is counted each time a page completes with no errors<\/li>\n<li>Failures &#8211; A failure is counted each time a page completes and at least one error was encountered<\/li>\n<li>Completions &#8211; A completion is counted each time a valid HTTP response is received from the server<\/li>\n<li>Failure Rate &#8211; the ratio of Failures to total attempts (Successes + Failures)<\/li>\n<\/ul>\n<p>With these new metrics, it is easy to see exactly how many pages succeeded and failed, as well as the total number of requests served (<em>Completions<\/em>) and the total number of attempts (the sum of <em>Successes<\/em> and <em>Failures<\/em>). The <em>Failure Rate<\/em> is clearly shown for each page and transaction &#8211; and is shown by default in the displays and reports wherever the <em>Errors<\/em> metric was shown in previous versions.<\/p>\n<p>Note that each error encountered (network, validation, etc) is still recorded as an individual entity, but they are not counted &#8211; since the number of errors is not generally valuable (for the reasons mentioned above).<\/p>\n<p>We hope this will clear up confusion faced by some users in previous versions of Load Tester!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Previous versions of Load Tester had 2 metrics describing the success or failure of a web page (or single transaction) during a load test: Repeats and Errors. A Repeat was counted any time a valid HTTP response was received from the server. Errors, however, were a bit more complex. Errors could occur at any point in the transaction, from establishing a connection to post-response validation. An error was counted if the connection was terminated in the middle of a transaction. It was also counted if the status code from the server indicated a failure (e.g. a 500 status). Validators record &hellip; <a href=\"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/2008\/10\/load-tester-improvement-better-success-and-fail-metrics\/\">Continue reading &raquo;<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[21],"class_list":["post-50","post","type-post","status-publish","format-standard","hentry","category-load-testing","tag-load-test"],"_links":{"self":[{"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/posts\/50","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\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/comments?post=50"}],"version-history":[{"count":10,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/posts\/50\/revisions"}],"predecessor-version":[{"id":60,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/posts\/50\/revisions\/60"}],"wp:attachment":[{"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/media?parent=50"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/categories?post=50"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/tags?post=50"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}