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
I find that, for n connections, wrk counts m less requests than the web server actually sees / logs, where m <= n.
This seems to be caused by wrk may stop without running the response_complete callback. Maybe wrk can run the last requests till complete, or indicate there are more requests hit the web server than which wrk knows have completed
The text was updated successfully, but these errors were encountered:
Thanks @ms2008! wrk no longer has a calibration phase, but requests could be in flight when the testing interval ends and wrk isn't going to wait for them to complete.
I find that, for n connections, wrk counts m less requests than the web server actually sees / logs, where m <= n.
This seems to be caused by wrk may stop without running the
response_complete
callback. Maybe wrk can run the last requests till complete, or indicate there are more requests hit the web server than which wrk knows have completedThe text was updated successfully, but these errors were encountered: