locust | 易学教程

Way to use locust.io by supplying user list

阅读更多关于 Way to use locust.io by supplying user list

I need to stress-test a system and http://locust.io seems like the best way to go about this. However, it looks like it is set up to use the same user every time. I need each spawn to log in as a different user. How do I go about setting that up? Alternatively, is there another system that would be good to use? Locust author here. By default, each HttpLocust user instance has an HTTP client that has it's own separate session . Locust doesn't have any feature for providing a list of user credentials or similar. However, your load testing scripts are just python code, and luckily it's trivial to

How often does python-requests perform dns queries

阅读更多关于 How often does python-requests perform dns queries

问题 We are using Locust to for load testing rest api services behind elastic load balancing. I came across this article regarding load balancing and auto scaling, which is something we are testing. Locust is using python-requests which is using urllib3 , so my question is if python-requests does a dns query for every connect, and if not, is it configurable? 回答1: Locust is using python requests that is using urllib3 that is using socket.getaddrinfo which has DNS caching disabled according to this

Locust.io: Controlling the request per second parameter

阅读更多关于 Locust.io: Controlling the request per second parameter

I have been trying to load test my API server using Locust.io on EC2 compute optimized instances. It provides an easy-to-configure option for setting the consecutive request wait time and number of concurrent users . In theory, rps = wait time X #_users . However while testing, this rule breaks down for very low thresholds of #_users (in my experiment, around 1200 users). The variables hatch_rate , #_of_slaves , including in a distributed test setting had little to no effect on the rps . Experiment info The test has been done on a C3.4x AWS EC2 compute node (AMI image) with 16 vCPUs, with