--no-reset-stats should be on by default

Please make this on by default. It is what most people will want in a realistic load test.

Case in point. We are gradually hatching about 1000 locusts that all need to authenticate with a login server. We hatch them slowly to avoid overwhelming the login server. After each locust logs in, it immediately starts performing our regular workflow. In our first test runs, we lost the stats that got collected during the hatch because we didn’t know --no-reset-stats existed. Watching your stats reset to 0 is extremely baffling. We had to scour the interweb to learn about this setting, and then spent a few hours figuring out how the switch works in a master/slave scenario

Making this on by default begs the question of how someone would turn it back off if they really do want to reset their stats when the hatch completes. Some options:

1. Ditch --no-reset-stats and replace it with a switch that has the opposite polarity : --reset-stats-on-hatch-complete
2. Just let me hook on_hatch_complete and reset the stats on my own if that is the behavior I want. Assumes that I can do this in my locust class or task set.

[heyman]

That is, alternative 1. Turn it off by default, and add a --reset-stats flag.

[bubbaksmith]

The most confusion/frustrating thing is that no where in the current documentation does it mention that all your data will reset after all Locust have been hatched.