Relevance of "throughput" in Performance testing
I Would like to know the Relevance of "Throuhgput" in performance testing>
By definition I know what is "Throuhgput" but I am unable to completly understand it's relevance in Performance testing.
1. Do we have to care about it when our focus is on Transaction Response times and CPU, Memory of App server, DB server?
2. Should there be a different strategy to test the "Throuhgput" as a metric ?
Appreciate any thoughts on this.
Re: Relevance of "throughput" in Performance testing
You should care about throughput as it shows the application can handle a certain amount of traffic and a degradation in that might not be seen by other metrics you have mentioned.
You can get approximately the same response time, CPU, memory but the throughout will be lower.
If you do not want to look at throughput, you can look at a different metric instead such, as transactions per seconds, hits per second, number of sessions opened against the applications, etc. All these measurements indicates about the workload the application can handle. Transaction response time, CPU, memory are performance indicators, not workload.