generating load versus processing time
Hi All, I am using loadUI 1.0.1 and soapUI 3.6.1 for performance testing our system. We have two different requirements that our system must satisfy. One is that our system has to deal with 14 co...
Forum Discussion
Hi Andy,
Thanks for your reply. I am not sure if I understand correctly but let me ask you this.
If our system should be able to process 14 transactions per second in a normal situation and 140 transactions per second in an extreme situation (as you said, to simulate a spike in usage) what components in loadUI should you use to test this.
With process I mean processing in the database. Our application logs the time of the incoming message and the time of the outgoing message and the difference between those times is the processing time that I talk about.
Currently I use the fixed load generator to simulate 14 concurrent users, but the result is that the application only processes about 2 requests per second in the database and not the required 14 per second. I feel that this approach is not the right way to go.
Any information is appreciated. I am just learning.
Ronald
Thanks for your reply. I am not sure if I understand correctly but let me ask you this.
If our system should be able to process 14 transactions per second in a normal situation and 140 transactions per second in an extreme situation (as you said, to simulate a spike in usage) what components in loadUI should you use to test this.
With process I mean processing in the database. Our application logs the time of the incoming message and the time of the outgoing message and the difference between those times is the processing time that I talk about.
Currently I use the fixed load generator to simulate 14 concurrent users, but the result is that the application only processes about 2 requests per second in the database and not the required 14 per second. I feel that this approach is not the right way to go.
Any information is appreciated. I am just learning.
Ronald
