distributed load testing
See original GitHub issueIs there support (or planned) for distributed load testing?
We currently use Locust which handles this quite nicely using master / slave mode:
locust -f my_locustfile.py --master
locust -f my_locustfile.py --slave --master-host=192.168.0.14
http://docs.locust.io/en/latest/running-locust-distributed.html
Issue Analytics
- State:
- Created 8 years ago
- Reactions:3
- Comments:12 (4 by maintainers)
Top Results From Across the Web
Distributed Load Testing on AWS | AWS Solutions - AWS
The Distributed Load Testing on AWS solution automates software applications testing at scale and at load to help you identify potential performance issues ......
Read more >What Is Distributed Load Testing? | SoapUI
Distributed load testing allows you to mimic the same behavior at different times against your environment outside of your own network.
Read more >Apache JMeter Distributed Testing Step-by-step
Apache JMeter Distributed Testing Step-by-step¶. This short tutorial explains how to use multiple systems to perform stress testing.
Read more >Distributed Load Testing | ReadyAPI Documentation
Distributed load testing is running a test on several different computers at a time. It makes possible simulating a large number of virtual...
Read more >Distributed load testing using Google Kubernetes Engine
To model this interaction, you can use Locust, a distributed, Python-based load testing tool that can distribute requests across multiple target ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s on the roadmap for
v2.0
, coming soon!@ianwalter Artillery Pro is only available on AWS right now, but Kubernetes support is on the roadmap which will make it available in non-AWS environments.
@abhayshankar As a workaround you can configure each Artillery instance to report runtime metrics to a central monitoring system, e.g. Datadog. It won’t give you full correct aggregation for e.g. response time distribution but may be close enough depending on your needs.