Risks Addressed Through Performance Testing

Speed related risks

Ensure that your performance requirements and goals represent the needs and desires of your users,

Compare your speed measurements against previous versions and competing applications.

Design load tests that replicate actual workload at both normal and anticipated peak times.

Conduct performance testing with data types, distributions, and volumes similar to those used in business 

operations during actual production

Include time-critical transactions in your performance tests.

Validate that all of the correct data was displayed and saved during your performance test.

Scalibility Related Risks

Compare measured speeds under various loads.

When you find a scalability limit, incrementally reduce the load and retest to help you identify a metric that can serve as a reliable indicator that the application is approaching that limit in enough time for you to apply countermeasures

Conduct performance tests beyond expected peak loads and observe behavior by having representative users and stakeholders access the application manually during and after the performance test.

Validate the functional accuracy of the application under various loads by checking database entries created or validating content returned in response to particular user requests.

Stability Related Risks

Take a server offline during a test and observe functional, performance, and data-integrity behaviors of the remaining systems.

Include error or exception cases in your performance test scenarios (for example, users trying to log on with improper credentials

Apply a patch to the system during a performance test

Force a backup and/or virus definition update during a performance test.

Make time for realistic endurance tests 

Source : Various websites