adadahs facebook adadahs twitter adadahs linkedin adadahs youtube
adadahs IT solutions Home Page adadahs IT solutions WebPage Development adadahs IT solutions Software Testing adadahs IT solutions Print Solutions adadahs IT solutions Animation Pages adadahs IT solutions Games adadahs IT solutions contact



Performance Testing is a controlled method of exercising artificial workload against a running system. The system can be hardware; software oriented or can be both. It is a type of testing intended to determine the responsiveness, throughput, reliability, and / or scalability of a system under a given workload.

Performance testing is commonly conducted to accomplish the following:

  • Assess production readiness.
  • Evaluate against performance criteria.
  • Compare performance characteristics of multiple systems or system configurations.
  • Find the source of performance problems.
  • Support system tuning.
  • Find throughput levels.

Need for Performance Testing


Performance testing is indispensable for managing certain significant business risks.

For example, if your Web site cannot handle the volume of traffic it receives, your customers will shop somewhere else.

Beyond identifying the obvious risks, performance testing can be a useful way of detecting many other potential problems.

While performance testing does not replace other types of testing, it can reveal information relevant to usability, functionality, security, and corporate image that is difficult to obtain in other ways.


Why Performance Testing


The great majority of modern applications, especially online, is focused on the mass, assumes operation of multiple users, and in such cases it is necessary to use performance testing under load, or more simply – Performance testing.

It helps to

  • Identify problems early on before they become costly to resolve.
  • Reduce development cycles.
  • Produces better quality, more scalable code.
  • Prevent revenue and credibility loss due to poor Web site performance.
  • Enable intelligent planning for future expansion.
  • Ensures that the system meets performance expectations such as response time, throughput etc. under given levels of load.
  • Expose bugs that do not surface in cursory testing, such as memory management bugs, memory leaks, buffer overflows, etc.
  Performance Testing

When is it required?


Design Phase:

Pages containing lots of images and multimedia for reasonable wait times. Heavy loads are less important than knowing which types of content cause slowdowns.

Development Phase:

To check results of individual pages and processes, looking for breaking points, unnecessary code and bottlenecks.

Deployment Phase:

To identify the minimum hardware and software requirements for the application.


What should be tested?


  • High frequency transactions: The most frequently used transactions have the potential to impact the performance of all of the other transactions if they are not efficient.

  • Mission Critical transactions: The more important transactions that facilitate the core objectives of the system should be included, as failure under load of these transactions has, by definition, the greatest impact.

  • Read Transactions: At least one READ ONLY transaction should be included, so that performance of such transactions can be differentiated from other more complex transactions.

  • Update Transactions: At least one update transaction should be included so that performance of such transactions can be differentiated from other transactions.
Performance Testing Bug  
adadahs web solutions  
adadahs Print solutions
adadahs Software Testing
2D Animations and Games
3D Animations
adadahs BroadCasting Ads
adadahs logo design   adadahs Brochure Design   adadahs PhotoEditing
Resolution 1280 * 1024
Copyright © adadahs All right reserved.
adadahs logo adadahs culture adadahs circle
adadahs Home


Contact Multimedia


Contact Accounts

Tours and Travels

Contact Tours and Travels


Contact Garments

Art and Craft

Contact Art and Crafts

Medical Tour

Contact Medical Tour