You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The front page of http://locust.io/ shows a web example of results where the totals row is a bit confusing. Some of the columns in the totals row is a sum of all numbers but not for others. For example the average column shows a total that is obviously not just a sum of all numbers. What is it a total of then? Perhaps it should be removed? This data isn't provided when you exit out of the process which gives text results without totals for that.
I found this on v0.7.5 and 0.8a2 available via pypi.
The text was updated successfully, but these errors were encountered:
I agree.. I consider the presence of "Total" for every column to be a bug and am labeling this issue as such.
my $.02 on this in Slack was:
"Totals should probably just be removed from the columns that represent timings because they don't really make any sense in that context. Is a sum of averages useful to users? (I doubt it)"
I agree that the wording "Total" is bad. However I do think it's useful to see an average of all the average response times. For example, if one has a lot of endpoints it might be easier to spot if one endpoint suddenly becomes really slow, by looking at the total average, instead of scanning the whole list.
What if we were to change the label to "Aggregated"? Then at least it wouldn't be untrue, even though we use different aggregation methods.
The front page of http://locust.io/ shows a web example of results where the totals row is a bit confusing. Some of the columns in the totals row is a sum of all numbers but not for others. For example the average column shows a total that is obviously not just a sum of all numbers. What is it a total of then? Perhaps it should be removed? This data isn't provided when you exit out of the process which gives text results without totals for that.
I found this on v0.7.5 and 0.8a2 available via pypi.
The text was updated successfully, but these errors were encountered: