You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Test was twice longer than requested (60 s instead of 30 s), "Requests/sec" is incorrect: test lasted 60 s instead of 30 s, made 301 requests (correct), so it is 5 requests per second (confirmed by server logs). And response times are incorrect compared to server logs (response times were are the same as in previous test).
The text was updated successfully, but these errors were encountered:
Test was twice longer than requested (60 s instead of 30 s), "Requests/sec" is incorrect: test lasted 60 s instead of 30 s, made 301 requests (correct), so it is 5 requests per second (confirmed by server logs).
I see the test lasted for 30 s because the log shows Total: 30.0014 secs. How did you measure the time to take the test?
And response times are incorrect compared to server logs (response times were are the same as in previous test).
--latency-correction simulates a user sending requests -q qps even when a user can't receive responses at that rate.
So if the results show a longer response time than the server log, it's OK because a log is started by when the user wants to connect (not actually connected).
I've found that in --latency-correction the DNS+dialup and DNS-lookup become incorrect. I'll fix it.
Test result without
--latency-correction
:Results looks correct. I've checked server log, and response times are correctly reported.
Test result with
--latency-correction
as recommended:Test was twice longer than requested (60 s instead of 30 s), "Requests/sec" is incorrect: test lasted 60 s instead of 30 s, made 301 requests (correct), so it is 5 requests per second (confirmed by server logs). And response times are incorrect compared to server logs (response times were are the same as in previous test).
The text was updated successfully, but these errors were encountered: