Forum Discussion
AndyHughes
14 years agoRegular Contributor
So to get this absolutely straight then, if this is my result data....
bearing in mind we said that each row represents the previous minutes data, we cant also say that Tps is the number of transactions in the last second, or is this the exception to the rule?
So my data which shows avg-tps of 82 in the first row represents everything that is available up to that point (which is only 200ms since I get a row per 200ms as set in the settings). So why isn't it the same as Tps? Tps says 72.7. Or am I asking too much of it?
It doesnt seem to me to be useful to have columns like Avg-Tps and Avg (which im presuming is the avg response time) covering the last minute of a test when there is a row per 200ms. The averages aren't useful if the load is being ramped up over this minute.
Maybe time to move to the Stats Workbench
bearing in mind we said that each row represents the previous minutes data, we cant also say that Tps is the number of transactions in the last second, or is this the exception to the rule?
So my data which shows avg-tps of 82 in the first row represents everything that is available up to that point (which is only 200ms since I get a row per 200ms as set in the settings). So why isn't it the same as Tps? Tps says 72.7. Or am I asking too much of it?
It doesnt seem to me to be useful to have columns like Avg-Tps and Avg (which im presuming is the avg response time) covering the last minute of a test when there is a row per 200ms. The averages aren't useful if the load is being ramped up over this minute.
Maybe time to move to the Stats Workbench
