Ensuring that an application will meet performance and scalability requirements when deployed requires performance testing. Without performance validation, there is great risk that the application will not provide the performance necessary to adequately support the business; this will result in customer dissatisfaction, lost business opportunity, and/or lost revenue. Most software development organizations recognize the need for performance testing, and many have invested in automated tools to help execute this testing. However, despite the commitment to testing and the investment in tools and resources, many organizations still have performance issues when their applications reach production deployment. The software doesn`t scale as expected; it doesn`t satisfy expected response times; and performance collapses under certain conditions or at certain stages of a transaction.
When these application performance failures occur despite testing, it is typically the result of a poorly defined or implemented performance testing practice. Setting up performance testing correctly is extremely challenging. It must accurately reflect such things as the expected population of application users, the number and frequency of tasks that will be executed, the distribution of those tasks, and the parallel activities that might compete for resources. Additionally, it requires well-defined and documented performance goals or requirements from which tests can be built. Without the right test model that reflects the full range of expected or actual usage and that has measurable performance criteria, performance testing will not be successful.
Developing an accurate usage model is key to en
Source:
http://www.wrox.com/WileyCDA/Section/Performance-Testing.id-291625.html
When these application performance failures occur despite testing, it is typically the result of a poorly defined or implemented performance testing practice. Setting up performance testing correctly is extremely challenging. It must accurately reflect such things as the expected population of application users, the number and frequency of tasks that will be executed, the distribution of those tasks, and the parallel activities that might compete for resources. Additionally, it requires well-defined and documented performance goals or requirements from which tests can be built. Without the right test model that reflects the full range of expected or actual usage and that has measurable performance criteria, performance testing will not be successful.
Developing an accurate usage model is key to en
Source:
http://www.wrox.com/WileyCDA/Section/Performance-Testing.id-291625.html
