Skip to main content

Goal of Performance Testing

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
For performance tuning basically we have two approach. In Approach1(white-box), we can do the following,
    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.
In Approach2(black-box), for a Web application, testers will use tools that simulate concurrent users/HTTP connections and measure the response times automatically. If the response time does not meet your expectations tuning has to be done at application/hardware/database level. In Tuning, First we need to enhance the application code efficiency, then we can optimize the database. If still your application doesn't meet your requirements then the following steps will help you.
    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

Popular posts from this blog

MoD / Raksha Mantralaya / Government Recommendation and Appreciation Letter

Dr. Manish Dhote (Patil) | Author | Economist | IT Lead

Dr. MANISH DHOTE (Patil) Ph.D. (Engineering) | Intl’ Acred. Ph.D. (Management) Intl’ MBA (Finance) Europe | BE (E&TC) COEP Dy. General Manager – JIO (Digital India | Digital Platform | IT) Contact@ +91 77688 34655 | 86606 94910 | twitter @mdhote Email@ edhote@gmail.com   | https://in.linkedin.com/in/manishdhote | https://manishdhote.blogspot.com/ | https://scholar.google.co.in/citations?hl=en&user=5n0ZVdoAAAAJ Author | Technology Leader | Economist| GST Technologist | Center of Excellence Head (Jio GST | Digital India Projects | Quality| IT) |Advisor | Political Analyst| Innovation Awardee Dr. Manish Dhote, Economist | Technology Leader | Author , is a recognized thought leader and trusted advisor in the GST, E-way Bill, Digital India Projects, Finance (Big size National | International Banks), 4G Telecommunication, Industry 4.0 Advisor, MNC Innovation Lab Advisor, India Stack Projects – G2C (Aadha...

SMAC, Digital Transformation, Innovation, Research and FinTech

Invitee and main speaker to talk about Industry 4.0, Digital Transformation, SMAC, FinTech topic.  Received International Research Trophy from one of top universality.