Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Feature request: Stepped hatch rate

See original GitHub issue

With a constantly increasing load due to a constant hatch rate, the server doesn’t have time to steady-state and produce stable statistics.

I would love to be able to specify a locust population that:

increases to a certain level (at the specified hatch rate),
remains at that level for a specified time,
increases to the next level,
remains at that level for a specified time,
and so on until the specified population is reached.

I think you would need two more parameters, in addition to hatch rate and number of locusts: population_step and time_between_steps.

It would make the population grow like this:

|            _________   _
|        ___/            _|  population step
|    ___/
|___/_______________

     |__| time between steps

Instead of like this:

|      __________
|     /
|    /
|___/____________

Issue Analytics

State:
Created 9 years ago
Reactions:1
Comments:7 (3 by maintainers)

Top GitHub Comments

4reactions

vladbezacommented, Mar 26, 2019

Found out that hatch rate may be set to float value so to get one user per 10 sec hatch rate 0.1 can be set. Maybe it will be helpful for somebody

1reaction

MattFishercommented, Jul 14, 2014

I would like to be able to set up a test run that will gradually increase load until the server hits its limits. At the moment, finding the maximum capacity of the server takes multiple sequential test runs with different numbers of locusts. Stepped hatching would allow a single test run to provide multiple loads in a single unattended test, sequentially, with time for the server to steady-state in-between. For reference, I’m using New Relic to monitor the results so I’m not focussed on extracting the statistics from Locust.

On 12 July 2014 23:59, Joakim Hamrén notifications@github.com wrote:

Hi Matt,

With a constantly increasing load due to a constant hatch rate, the server doesn’t have time to steady-state and produce stable statistics.

This is the reason why Locust will reset the statistics after the hatching phase is completed. I’m not sure why stepped hatching would make any difference in this regard.

— Reply to this email directly or view it on GitHub https://github.com/locustio/locust/issues/168#issuecomment-48812180.