In my today's blog, user can find interesting discussion on performance testing and its approaches. Please go through my posting and next time we can share some interesting more stuffs. Enjoy testing:)
The goal of performance testing is not finding bugs, but to remove the bottlenecks from the application and improve the efficiency.
Before doing a performance testing we basically need to know the following points
- 1. Expected no of concurrent users or HTTP connections with your application
2. Acceptable response time for your pages
- Code Analysis, We can search for poor algorithms or looping which is the reason for inefficiency.
Database Analysis, We can use query optimizers and profilers to optimize the database.
Hardware & Network, We can use utilities such as top, iostat to monitor hardware resources and ntop, netstat to monitor the network and Sockets.
- 1. Using cache mechanisms.
2. Publish highly requested pages statically, so that they don't hit the database.
3. Scaling Web servers horizontally via load balancing.
4. Scaling database servers horizontally and split them into read/write servers and read-only servers.
5. Scale the servers vertically by adding more hardware resources (CPU,RAM)
Points to remember,
We should take care such that one variable is modified at a time and redo the measurements.
Functionally the application should be well tested and must be in good quality. i.e., the software under test is already stable enough so that performance testing process can proceed smoothly.
Comments