Don't reset stats after hatching is complete

[drewtunes]

The stats reset when hatching starts already and if you hatch slowly, there can be many tasks completed by the time hatching completes. Without this change, those completed tasks are removed from the stats as soon as hatching completes.

[Jahaja]

I do not understand what the problem is with resetting the stats after hatching is complete. This is the normal behaviour of locust for quite some time now. Could you explain it further?

[drewtunes]

The problem I ran into was that several requests had already been made by the time hatching was complete. If I hatch 90 users at one per second, by the time the 90th user hatched, the first user had already made several requests. By resetting statistics after hatching is complete, the early requests are lost from the statistics.

Sent from my mobile device.

On Jul 9, 2014, at 5:42 PM, Joakim Hamrén [email protected] wrote:

I do not understand what the problem is with resetting the stats after hatching is complete. This is the normal behaviour of locust for quite some time now. Could you explain it further?

—
Reply to this email directly or view it on GitHub.

[Jahaja]

This is the intended behaviour. The hatching phase will normally contain a good amount of overhead for warming up caches on the target, logging in users, etc. Thus, after the hatching is complete, locust will reset the stats to make sure that we only measure stable, warmed-up, requests.

[spearsem]

Can this be made configurable? Some load tests may be used to see how throughput and latency vary as the number of users increases, up to an expected saturation point, and traffic prior to fully hatched point will still be meaningful (and will not suffer from unwarm caches, etc., by design).

[heyman]

@spearsem It is configurable in Locust >= 0.8. Use the —no-reset-stats option.