Yes, we love you Locust - but why don’t show us the right RPS in the stats!? Here is a workaround.

As many users have found (hoangphucITJP reported), there is a strange behaviour in current version of Locust, where “Total Requests per Second” graph RPS drops to cero after some time after the test started, despite the RPS number on the header keeps rising (pic below):

User klloveal realized that “the /stats/request endpoint stops returning the ‘Total’ stat block at the end of the stats list”. With that in mind, I had a look at /stats/request response and realized that the header RPS was being filled by a different variable called ‘report.total_rps’ - ipso facto, the following super simple change:

That’s it!

Coward disclaimer: I don’t know if this change could have other consequences and it is not addressing the root cause.

Keep reading

  • Locust
  • kStress: An implementation of Locust to stress Kaltura’s eCDN