Docker Image Locust.io Docker Image

eva2000 · Jul 7, 2017

Been a while since I posted in Centmin Mod Docker development sub forums. So posting a new Locust.io load testing Docker image I just whipped up for quick testing https://github.com/centminmod/docker-ubuntu-locust.

I used Locust.io 2+ yrs ago for Wordpress7 load testing.

I created this Locust.io Docker image as my favourite load testing service Blitz.io is shutting down. So that leaves with my Siege benchmark tool which you can see some old benchmarks listed on official site's benchmark page. Example for Wordpress 7 Siege benchmarks. Centmin Mod automatically includes Siege benchmark tool installs already

So that leaves me with looking for other tools like Locust.io. You can find the Ubuntu 17.10 based Locust.io Docker image details at GitHub - centminmod/docker-ubuntu-locust: Docker image for locust.io load testing.

No support provided by me, so read Locust.io documentation. Writing test configs requires Python coding knowledge though.

What is Locust?
Locust is an easy-to-use, distributed, user load testing tool. It is intended for load-testing web sites (or other systems) and figuring out how many concurrent users a system can handle.

The idea is that during a test, a swarm of locusts will attack your website. The behavior of each locust (or test user if you will) is defined by you and the swarming process is monitored from a web UI in real-time. This will help you battle test and identify bottlenecks in your code before letting real users in.

Locust is completely event-based, and therefore it’s possible to support thousands of concurrent users on a single machine. In contrast to many other event-based apps it doesn’t use callbacks. Instead it uses light-weight processes, through gevent. Each locust swarming your site is actually running inside its own process (or greenlet, to be correct). This allows you to write very expressive scenarios in Python without complicating your code with callbacks.
Click to expand...

Background
Locust was created because we were fed up with existing solutions. None of them are solving the right problem and to me, they are missing the point. We’ve tried both Apache JMeter and Tsung. Both tools are quite OK to use; we’ve used the former many times benchmarking stuff at work. JMeter comes with a UI, which you might think for a second is a good thing. But you soon realize it’s a PITA to “code” your testing scenarios through some point-and-click interface. Secondly, JMeter is thread-bound. This means for every user you want to simulate, you need a separate thread. Needless to say, benchmarking thousands of users on a single machine just isn’t feasible.

Tsung, on the other hand, does not have these thread issues as it’s written in Erlang. It can make use of the light-weight processes offered by BEAM itself and happily scale up. But when it comes to defining the test scenarios, Tsung is as limited as JMeter. It offers an XML-based DSL to define how a user should behave when testing. I guess you can imagine the horror of “coding” this. Displaying any sorts of graphs or reports when completed requires you to post-process the log files generated from the test. Only then can you get an understanding of how the test went.

Anyway, we’ve tried to address these issues when creating Locust. Hopefully none of the above pain points should exist.

I guess you could say we’re really just trying to scratch our own itch here. We hope others will find it as useful as we do.
Click to expand...

eva2000 · Jul 7, 2017

Standalone mode

Distributed mode with 1x master + 3x slaves

Log in / Register

Forums

Join the community today

Docker Image Locust.io Docker Image

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

.

Log in / Register

Useful Searches

Join the community today

Docker Image Locust.io Docker Image

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

.