Things We Need to keep In Mind While Doing Performance testing

1. Test Early And Test Often: We always follow our testing process means we try to work as per the STLC rules and according to the bug life cycle. If there is a bug then it should be resolved by developer then review by any of peer and after that testing process comes into the picture.
but sometimes, mostly in the case of performance testing we do need to start testing as soon as possible and it should be iterate in overall development cycle.
by doing this we could predict the problem early.

2. Attention on end user not only on number of server: We should focus on number of user except focusing on number of server. because our motive for performance testing is not only to check the timing while we need to focus on end user expectations and business requirement as well.

3. Create Realistic Tests: Evaluating how a software application will react in a real world situation is necessary to assure the success of performance testing, So creating practical test that keep variability in mind and taking into consideration the verity of device and client environment to access the system is required.

4. Performance is Relative: Performance might indicate something to you and something else to the user. user are not sitting with a stopwatch to measure the load of time. what the user wants is to get helpful data fast and for this , it is necessary to include the client processing time when covering load time.

5. Quantifying Performance Metrics:

• The expected response time – Total time taken to send a request and get a response.
• The average latency time.
• The average load time.
• The longest time taken to fulfill a request.
• Estimated error rates.
• The measure of active users at a single given point in time.
• Estimated number of requests that should be handled per second.
• CPU and memory utilization required to process a request.