Quality is delighting customers
Some of the parameters to measure performance of an application can be as following:
Number of users to support system
Response time per page
Response time of whole system
What other measures should be considered while doing performance testing?
Of course you need to consider the initial conditions, e.g. server configuration, network configuration, and amount of data already in the database.
"Number of users to support system" can mean different things, e.g.
Most applications perform multiple operations. You have to decide which operations (or mixtures of operations) you want to measure. Different operations will have different performance characteristics. Moreover, since operations may share the same database, operations of different times may interfere with each other.
As you measure response time, you may also want to measure how the server is behaving, e.g. cpu utilization, memory consumption, network utilization, disk space consumption, disk I/O rates. Your ability to measure these in isolation will depend on whether other applications are running on the machine, whether the machine is physical or virtual, etc.
I hope that helps.
Thanks a lot for your detailed guidance
What other measures (which you already derived 4 of them out of my 1 identified) can be used to measure the performance? Although, you mentioned that it is your need that identifies which measure you want to derive, but my concern is to learn the measures and then consider what will best fit the application need.
I hope you understood my point.
Moreover, can you share the impact of performance on cpu utilization, memory consumption, network utilization, disk space consumption, disk I/O rates and others (if applicable).
e.g. the more cpu utilization, the more the system is nearing to crash or system slowing down.
similarly, the more memory consumption, the less the system response
and so on.