

Busy and idle threads - Do you need more Web servers? More worker threads? Do you have an application performance hotspots slowing you down?.Web server metrics help you find errors in your API deployment, so you can scale and augment as needed: Load Testing Metric #1: Web Server Metrics Now that you know these key load testing terms, we break down how these will play out for you and your load testing results and where they are testing which parts. How many actual users do you predict will access your system at once?.Single user - Only one transaction completed.Concurrent user - Runs through a transaction from start to finish then repeats.Also find your peak traffic time (perhaps holiday rush?), then increase with percentages of expected traffic growth Peak-hour pageviews - Your base can come from your Web analytics tool (like Google Analytics).Session length - A group of interactions that took place on your website at a certain time, like how long did someone spend on your app or website, including jumping around to different pages.Virtual Users (VUs) - A certain number of users simultaneously accessing your system or a certain number of users accessing from different browsers.Throughput - often bandwidth consumed, but, in general, the maximum rate at which something can be processe.

Requests per second - how many requests for HTML pages, CSS stylesheets, XML documents, JavaScript libraries, images, Flash/multimedia files, etc.Concurrent users - many virtual users are active at any given time.

