Hi Gagandeep, there are spikes in throughput during ramp up of our test which I believe is normal to have but once all users are up and running we see a drop in throughput and it settles at a point for the rest of the test. we dont see any issue with memory, disc, CPU.. Throughput and hits are stable during steady state of the test, able achieve the no.of transactions SLA for all scenarios but some of the transactions have got very high response times than SLA while some of the transactions have response time within SLA. does this mean code changes required to have better response times for these transactions.
Hi Gagandeep, there are spikes in throughput during ramp up of our test which I believe is normal to have but once all users are up and running we see a drop in throughput and it settles at a point for the rest of the test. we dont see any issue with memory, disc, CPU.. Throughput and hits are stable during steady state of the test, able achieve the no.of transactions SLA for all scenarios but some of the transactions have got very high response times than SLA while some of the transactions have response time within SLA. does this mean code changes required to have better response times for these transactions.
ReplyDeleteThanks,
Veera.
Hi Veera,
DeleteI would suggest to analyse the server connection pool. Such issue comes when server unable to serve all the requests at an expected rate.