Merge pull request #185538 from ntrogh/patch-4

Clarified RPS calculation

Author: PRMerger9

articles/load-testing/how-to-high-scale-load.md

@@ -26,11 +26,11 @@ In this article, learn how to set up a load test for high-scale load by using Az
 
 ## Determine requests per second
 
-The maximum number of *requests per second* (RPS) that Azure Load Testing can generate depends on the application's latency and the number of *virtual users* (VUs). 
+The maximum number of *requests per second* (RPS) that Azure Load Testing can generate depends on the application's *latency* and the number of *virtual users* (VUs). Application latency is the total time from sending an application request by the test engine to receiving the response.
 
-You can apply the following formula: RPS = (# of VUs) * (1/latency).
+You can apply the following formula: RPS = (# of VUs) * (1/latency in seconds).
 
-For example, if application latency is 20 milliseconds (ms), and you're generating a load of 2,000 VUs, you can achieve around 100,000 RPS.
+For example, if application latency is 20 milliseconds (0.02 seconds), and you're generating a load of 2,000 VUs, you can achieve around 100,000 RPS (2000 * 1/0.02s).
 
 Apache JMeter only reports requests that made it to the server and back, either successful or not. If Apache JMeter is unable to connect to your application, the actual number of requests per second will be lower than the maximum value. Possible causes might be that the server is too busy to handle the request, or that an TLS/SSL certificate is missing. To diagnose connection problems, you can check the **Errors** chart in the load testing dashboard and [download the load test log files](./how-to-find-download-logs.md).