We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
hi,九毫,问一下关于使用locust的问题,httprunner是基于locust的,经过我测试发现locust在并发数的测试上似乎非常耗cpu,4c8g机器,在jmeter我可以跑到300以上的并发,使用locust一个cpu只能并发模拟15个左右的协程,用locust只能做到60个左右的并发,在并发测试上差距还是挺大,实际工作中使用locust来测试并发的时候加的机器看起来要是jmeter的好几倍?
The text was updated successfully, but these errors were encountered:
据我了解locust使用的是协程的并发方式,比jmeter的线程方式效率还要高,我本机做过简单的测试,mac pro 16G 四核,四个slave,100个user可以达到600 RPS,而且cpu还比较低,估计是服务器端返回不够快了
Sorry, something went wrong.
Merge pull request #91 from bbx-winner/main
8cc2450
fix: broadcast to all rendezvous at once when spawn done
bbxwinner
No branches or pull requests
hi,九毫,问一下关于使用locust的问题,httprunner是基于locust的,经过我测试发现locust在并发数的测试上似乎非常耗cpu,4c8g机器,在jmeter我可以跑到300以上的并发,使用locust一个cpu只能并发模拟15个左右的协程,用locust只能做到60个左右的并发,在并发测试上差距还是挺大,实际工作中使用locust来测试并发的时候加的机器看起来要是jmeter的好几倍?
The text was updated successfully, but these errors were encountered: