Open Vanav opened 1 year ago
Thanks for the issue!
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.
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?
- First line of tui shows strange:
60 s / 30 s
— counting after it should stop- Logs on server: first line on 06:29:18, last line on 06:30:19
From server logs I got the same response times in both tests. So I still don't get why reported stats are different.
@Vanav I've fixed the duration of a test. Could you check it with the master branch?
@hatoo once you've fixed this issue a log time ago and you did not receive the feedback from @Vanav I do believe that you should closed it, what do you think? I am just recommend it, because I like to see the most updates issues to see if is there any opportunity that I can contribute. Although, it's just a suggestion
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).