Website Performance Analysis Based on Component Load Testing: A Review
2 Charu Babbar Neha Bajpai Centre for Development of Advanced Computing ,Noida 2 Centre for Development of Advanced Computing ,Noida 1 babbar.charu@gmail.com, 2nehakapoor@cdacnoida.in 1 1
Abstract-Developers typically measure a Web applications quality of service in terms of response time, throughput, and availability. Poor QoS translates into frustrated customers, which can lead to bad opportunities. One way to assess IT infrastructure performance is through load testing, which assess how the website supports its expected workload by running specified set of scripts that emulate behavior at different load levels. This paper addresses the website performance analysis based on component load testing with different QoS measures.
1. Introduction
The Goal of a Load test is to uncover functional and performance problems of a system under load. Performance problems refer to the situations where a system suffers from unexpectedly high response time or low throughput. It is difficult to detect performance problems in a load test due to the absence of formallydefined performance objectives and the large amount of data that must be examined. When we develop a hightraffic Website, a Web service, or some other server components, then we can see that how much load the site or service can handle. Performance is defined as the time between the submission of a request from a user and the completion of the response. In effect, it is the mean response time that a single HTTP request of a web application system spends from end to end. This measure is one of the critical factors in the evaluation of web services. A performance test can help determine whether the product meets the performance goals. For performance test reporting, four types of information may be provide: Latency for each type of request Throughput information, or how much load server received(for example, requests per second) Server-side resource utilization( such as CPU usage, memory consumption, and so on. Test run configurations
Performance of many website depends on the load on the application at peak time under varying conditions. Performance testing is normally conducted in a reasonably simulated environment with the help of Performance testing tools. However Performance of Web application and Website depends on various parameters and each parameter must be tested under varying stress levels. Different parts of the Website must be tested with different parameters under varying condition and stress levels. In such circumstances, it is necessary to decompose the website into many components, which represents the behavior of various components. Although we can evaluate the performance of website by testing the complete page but this may not be a good idea for two reasons. First, when we evaluate the WebPages and websites, it does not specify the reason for not loading a web page if any. Second, it does not specify the link or an item detail where the maximum time has been spent when we check the performance of WebPages and website. Therefore, there is need to test the individual components through which the performance of the said components can be evaluated.
2. Load Testing
The time website takes to load a webpage in a browser so that all the elements of the page can be viewed. The time depends on a number of factors including the amount of network traffic, amount of video, audio, graphic and animation technology on the page. It is the process of putting demand on a system device and measuring its response. Load testing is performed to determine a systems behavior under both normal and anticipated peak load conditions. It helps to identify the maximum operating capacity of an application as well as any bottlenecks and determine which element is causing
degradation. When the load placed on the system is raised beyond normal usage patterns, in order to test the systems response at usually high or peak loads, it is known as Stress Testing.
Figure 2: Website Loading Scenario Figure 1: The Load-testing process.
4. Test Objectives of Load Testing
In Figure 1, The script recorder creates user interaction scripts based on actual requests. The load generator then sends a realistic load, based on scripts and test parameters, to the website, and the performance monitor measures its performance. Many concurrent users running the same application to see whether a system handles the load without compromising functionality or performance. Measurement of no. of concurrent users that can the system handle without increase in the expected response time. Parameters affecting the Load Testing are as follows: System Requirements Response Time Think Time Work Load Locate and resolve potential problems before it hits on the users. Performance is the key to success of any web based application. Load test will able to provide the maximum capacity, the system can handle for an application. Transaction Mix Throughput
3. Requirement of Load Test:
The failure of a mission- critical web application can be costly. Assure performance and functionality under real world conditions.
4.1 System:
Figure 5: Think Time for Load Testing of Websites
4.4 Work Load: Work Load depends on the
following factors which are as follows:
Figure3: System Requirements in Load Testing of Websites
Number of users Transactions
4.5 Througput: The amount of work that can be 4.2 Response Time: Time in which the system
responds for a particular transaction request. performed by a system or component in a given period of time. Throughput depends on following factors: Transactions/sec Web Interactions/sec Pages/sec Bytes/sec
5. Steps involved in Load Testing:
Planning Load Tests:
o Information that is required for load testing a system. o Organizing the system information collected o Using the information effectively to carry out load tests.
Figure 4: Response Time for Load Testing of Websites
Creating VUsers (Virtual User Technology)
Simulates a real user Requires less resources- machines and people Greater control over test execution
4.3 Think Time: Time taken for selecting a new transaction after
the response for the previous transaction has been received.
o Can synchronize actions performed by users o Collect and analyze results in a better way o Vusers can communicate directly with a server by executing calls to the server API- without relying on client software.
Performance testing is the process to determine the speed or effectiveness of a computer, network, software program or device. In other words, Performance testing is to evaluate the response time (speed), throughput and utilization of system to execute its required functions in comparison with different versions of the same product or a different competitive product, This is done to derive benchmark .The factors that governs Performance testing are as follows: Throughput Response Time
7. Test Objectives of Performance Testing
Identifies problems at an early stage before they become costly to resolve. code. Reduces development cycles. Produces better quality, more scalable
Figure 6: Virtual user generator in the Loading of Websites
Prevents revenue and credibility loss due to poor web site performance. Enables intelligent planning for future expansion. To ensure 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.
o o o o
Capture a business transaction by recording user actions performed. Monitors the communication between the application server Generate the required function calls Inserts the generated function calls into a Vuser script
Recording of Script
o New Vuser o Recording Options Recording Mode: This allows us to specify the information to be recorded and which functions to be used when generating a script HTML Mode: HTML mode is based on user actions and the scripts contain functions that correspond directly to the action taken. URL Mode: URL mode is based on HTTP requests sent to the server as a result of user actions.
8. Requirements of Performance Testing :
At various phases requirement of performance testing are as follows:
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.
6. Performance Testing
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 application. software requirements for the
REFERENCES
[1] Qinglin Wu,Performance Testing and
Optimization of J2EE-based Web Applications, Second International Workshop on Education Technology and Computer Science, IEEE, PP.681-683, 2010.
9.
Proposed Approach for Load andPerformance Testing of Website:
[2] Zao-Bin GAN and Deng-Wen WEI, Vijay VARADHARAJAN, Evaluating the Performance and Scalability of Web Application systems Third International Conference on Information Technology and Applications(ICITA05),IEEE,2005. [3] B.M. Subraya and S.V. Subrahmanya, Object driven Performance Testing of Web Applications, 13th International Quality Week 2000 Software Quality Week 2000, IEEE,May 30 June 2, 2000. [4] Daniel A. Menasce,Load Testing of Websites, http:/computer.org/internet, IEEE Internet Computing, PP.70-74, July-August 2002. [5] Zhen Ming Jiang, Ahmed E. Hassan and Gilbert Hamann and Parminder Flora, Automated
Performance Analysis of Load Tests, Proc. ICSM 2009, Edmonton, IEEE, Canada, pp.125-134, 2009.
10. Conclusion
Based on identified parameters, proposed Approach will be able to calculate the Load and Performance of the complete Website with the individual components performance.
[6] Steven Haines Senior, "Performance Testing Methodology, IEEE International Conference on Information management, October 2005. [7] J.D. Meier, Carlos Farre A Hantbansod, Scott Barber And Dennisrea,Performance Testing
10. Acknowledgement
The author sincerely thank to Mrs. Neha Bajpai(Project guide) and to friend who helped me in conducting the [8] approach and calculating the results during performance analysis.
Guidance for Web Applications , World Academy Of Science, Engineering And Technology, 2005.
of IT implementation experience. Presently, she is working as a Senior Faculty in School of IT at
[8] Charu Babbar, Neha Bajpai, A Survey on Evaluating Performance of Web Application
Centre for Development of Advanced Computing (CDAC), Noida. Her present interests are in the subjects related to Object Oriented Analysis & Design, UML, Software Testing, Object Oriented Technologies (Java Programming) and Object Oriented Database Management System. She has worked on various projects in her ten years of teaching and software implementation time span. She has over 10 research papers out of which three are in international journals and rests are in international
Performance, International Conference on Reliability Infocom Technology and Optimization, ICRTIO2010, 4th November [9] Charu Babbar, Neha Bajpai, Web Application Performance Analysis Based on Component Load Testing, International Journal of Technology and Applied Science, IJTAS,Vol. 2, pp. 22-28, 2011 WEB REFERENCES : Modeling the real world for load testing websites by
(http://www.methodsandtools.com/archive/archive.php?id=38) Steven Spline http://www.testingfaqs.org/t-load.html http://www.opensourcetesting.org http://www.sharewareconnection.com/testing- master.htm
. CHARU BABBAR completed M.Sc (C.S.E.) from Guru Jambheshwar University,Hisar in 2007 and has 2 yrs. Industrial experience. Now Currently pursuing M.Tech(I.T.) from CDAC-Noida and working on project based on Software Testing. The area of interests are in the subjects related to Software engineering and Software Testing. She has published and presented 1 research paper in international conference and 1 research paper in international journal. Email id: babbar.charu@gmail.com
2.
Mrs. NEHA BAJPAI received
M.Tech in Information Technology in the year 2005. She has nine years of teaching and one year
