Forum Discussion
AndyHughes
14 years agoRegular Contributor
Hi Ronald,
That may well be the case. So if your fixed load generator is maintaining a load of 14 (you can see if it is in the runner component. Sometimes even though you have selected a fixed load of 14 you may not be running 14 concurrently, this would depend on the interval you have selected in the fixed load generator. If this is not low enough, it may not be 'releasing' the requests at a high enough rate to ever get to 14 concurrent requests.) But if it is, and you are only processing 2 per second then it may be that your service is just slower than you would like and only 2 complete per second.
I'd be looking at the average time output on a table log and multiplying that by 14 to see if it is greater than 1 or multiply by 140 in the second scenario.
The actual set-up should be straight forward and I don't think you are doing anything wrong. Generator, Runner, stats module, table log, I think that's all you need.
Andy
That may well be the case. So if your fixed load generator is maintaining a load of 14 (you can see if it is in the runner component. Sometimes even though you have selected a fixed load of 14 you may not be running 14 concurrently, this would depend on the interval you have selected in the fixed load generator. If this is not low enough, it may not be 'releasing' the requests at a high enough rate to ever get to 14 concurrent requests.) But if it is, and you are only processing 2 per second then it may be that your service is just slower than you would like and only 2 complete per second.
I'd be looking at the average time output on a table log and multiplying that by 14 to see if it is greater than 1 or multiply by 140 in the second scenario.
The actual set-up should be straight forward and I don't think you are doing anything wrong. Generator, Runner, stats module, table log, I think that's all you need.
Andy
Related Content
- 10 months agojamescollett
- 2 years agovericomms