[Resolved] Request count is not correct
I'm running a load testing for 120 hours duration. I was watching the request count for each call and it's showing way off. For example - Requests: 72562 Running: 23 Completed: 72578 Failed: 718...
Forum Discussion
If you read the article at the link above your post, it explains the counts clearly. I was confused too at the beginning to be honest.
To give an explanation to your scenario quickly, discard happens when 'running' and then 'queued' for that runner fills up. For example, lets say your runner has setting of 10 concurrent thread to run, and 100 as queue. Now generator starts generating load, so they go in 'running', if response doesnt come soon enough, then running count will start increasing. When it reaches 10, any subsequent generated request will go to 'queued'. If 'running' goes below 10 (your setting), then requests from 'queued' will go in 'running' state. Now if 'queued' also gets filled up, then any subsequent generated request will get discarded.
So basically,
Requests = Running + Queued + Completed + Discarded
Failed is just an informational number. Doesn't get counted in that equation (though IMO it should).
But I do agree, from your example it seems the counts are indeed wrong. As per the flow chart (shown in the linked page), discarded shouldn't count towards completed. But it seems it did.
Also I think the flowchart should be updated a bit. Instead of 'Send Request', it should say 'Run Test Case' and instead of 'Response Received or Timed Out', it should say 'Test Case Run Finished or Timed Out'. The reason is, if there's a failure in test case step execution, even then the failure count gets increased.
To give an explanation to your scenario quickly, discard happens when 'running' and then 'queued' for that runner fills up. For example, lets say your runner has setting of 10 concurrent thread to run, and 100 as queue. Now generator starts generating load, so they go in 'running', if response doesnt come soon enough, then running count will start increasing. When it reaches 10, any subsequent generated request will go to 'queued'. If 'running' goes below 10 (your setting), then requests from 'queued' will go in 'running' state. Now if 'queued' also gets filled up, then any subsequent generated request will get discarded.
So basically,
Requests = Running + Queued + Completed + Discarded
Failed is just an informational number. Doesn't get counted in that equation (though IMO it should).
But I do agree, from your example it seems the counts are indeed wrong. As per the flow chart (shown in the linked page), discarded shouldn't count towards completed. But it seems it did.
Also I think the flowchart should be updated a bit. Instead of 'Send Request', it should say 'Run Test Case' and instead of 'Response Received or Timed Out', it should say 'Test Case Run Finished or Timed Out'. The reason is, if there's a failure in test case step execution, even then the failure count gets increased.
