|
|
Today, Web applications/Web sites get a great deal of traffic. To effectively handle the traffic and offer improved performance for business-critical Web applications, companies need to predict the maximum load the web server can adequately handle using a distributed architecture. To measure the performance of such a system, QEngine provides the Distributed Load Testing option.
Understanding Distributed Load Testing
QEngine distributed load testing generates load from one single Test Controller and simultaneously distributes the configured load in the remote play engines. The distributed playback engine has the following components:
Test Controller
Test Controller is the machine were QEngine is installed. The functions of Test Controller are as follows:
Generates and distributes the load (Max Users configured in the Add Play Engine Screen) in remote machines with different hardware configurations.
Starts the load test execution in the distributed play engines.
At the end of the test execution, automatically collects the test logs generated in the distributed play engines and stores it in the respective directories.
QEngine Distributed Play Engines
Distributed play engines are the machines where QEngine is installed with RMI Server for remote test execution. The functions of play engines are as follows:
The play engine is where the user requests sent by the Test Controller is replayed to measure the performance statistics.
The play engine automatically stores the test reports generated during the load test execution in the common database.
Common Database
The common database is used both by the Test Controller and the distributed play engines. The user requests generated for the configured test parameters, the responses received from the distributed play engines and the test reports generated and sent by the distributed play engines are stored in the common database.
Steps to enable Distributed Load Testing
The steps to enable distributed playback are as given below:
Note: You can skip steps 1 to 3, if you have already recorded the business cases and configured the test parameters for load test execution.
Record the business cases as per the steps given in the topic Recording Business Case.
Parameterize the recorded URLs (if required) as per the steps given in the topic Handlng URL Parameters.
Define test parameters such as user profiles and workloads. Configure server monitoring and virtual Ips (optional). Create test cases to associate the profiles and workloads. To know the details, refer to the steps given in the topic Defining User Profiles, Defining Workloads, Configuring Server Monitoring, Configuring Virtual IP Addresses and Creating Load Test.
Install QEngine in a machine which acts as the Test Controller.
As per your requirements to distribute the load, install QEngine in machines with different hardware configurations. Start remote agent in each of the distributed machines using StartDistributedAgent.bat/.sh file in <QEngine_Home>/bin directory.
Open Web Performance Test Studio from Test Controller, choose Play->Play Settings menu item from the menu bar. In the Other Details panel, select the check box Distributed Playback and click OK.
Choose Play->Add Play Engine menu item from the menu bar. The Play Engine Configuration screen will be displayed.
In this screen, configure the IPs, RMI port and maximum virtual users to be simulated in the distributed play engines. This is to enable the Test Controller to remotely contact the distributed play engines to perform distributed load testing. For details of configuring Play Engine IPs, Port, and Max Users, refer to the context-sensitive help in the following link.
After configuring the IPs, Ports, and Max Users, start the load test execution as per the steps given in the topic Executing Load Test.
The test reports will be stored in the common database. The test logs will be stored in the respective directories in the Test Controller. To know the report details, refer to the topic Load Test Graphs/Reports.
|
|