-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comparison of performance test results between locust and jmeter #859
Comments
From Jmeter's page it explains it as number of requests per second, which means the same with Locust.
|
@gunesmes I do a perf test ,but i am confused about the result |
Locust's number of requests is defined by the number of locusts, the time the ops take, and the taskset weighttimes. If you have 10 locusts with a min/max weight of 1000ms between tasks and each operation takes 1 second, you will make 5 requests/second - each locust will:
The paradigm for Locust is simulating user workflows. If you want to check "maximum req/sec" you will want to reduce the minimum/maximum weight times to close to 0ms. |
throughput is a rate.. like requests/sec. |
the reason you see a massive difference is that there is a configurable wait time between requests in locust and you likely dont have something similar in your jmeter tests. if you set the wait time to 0 you would see more similar results. closing this issue since there is nothing actionable here. |
@aldenpeterson-wf @cgoldberg thank u very much~ |
@gunesmes @aldenpeterson-wf @cgoldberg |
Description of issue / feature request
I use jmeter and locust do the same perf test ,but difference of the test results between locust and jmeter is huge.
Jmeter result: Throughput 50/sec
Locust result: Requests 100/s
How to define "requests" in locust? what's the difference between throughput and requests?
Steps to reproduce (for bug reports)
TBD - example code appreciated
The text was updated successfully, but these errors were encountered: