LoadRunner introduction and video tutorial

1 Overview LoadRunner is an industrial standard load testing tool that predicts system behavior and performance. LoadRunner can test the entire enterprise architecture by simulating tens of millions of users to implement concurrent loads and real-time performance monitoring. By using LoadRunner, enterprises can minimize test time, optimize performance, and accelerate the release cycle of application systems. Enterprise network application environments must support a large number of users. The network architecture includes various application environments and different vendors provide software and hardware products. Unpredictable user loads and increasingly complex application environments make the company always worry about slow user response and system crashes. These all inevitably lead to losses to the company's earnings. Mercury Interactive's LoadRunner allows enterprises to protect their own sources of revenue without buying additional hardware to maximize the use of existing IT resources, it also ensures that end users have a good evaluation of the quality, reliability, and scalability of their testing applications in all aspects of the application system. LoadRunner is an automatic load testing tool suitable for various architectures. It can predict system behavior and optimize system performance. LoadRunner's testing object is the entire enterprise system. It simulates the actual user's operation behavior and implements real-time performance monitoring to help you find and discover problems faster. In addition, LoadRunner supports extensive protocols and technologies to provide special solutions for your special environment. 2. LoadRunner is the testing object of the entire enterprise system. It simulates the actual user's operation behavior and implements real-time performance monitoring to help you find and discover problems faster. In addition, LoadRunner supports a wide range of protocols and technologies to provide special solutions for your special environment. [1] 3 main functions: Using LoadRunner's Virtual User Generator, you can easily create system loads. This engine can

LoadRunner Performance Virtual User Simulation Test

It can generate virtual users and simulate the business operations of real users in the form of virtual users. It first records the business process (such as placing an order or booking a ticket) and converts it into a test script. With Virtual users, you can generate tens of thousands of users simultaneously on Windows, un ix, or Linux machines. Therefore, LoadRunner can greatly reduce the hardware and human resources required for load testing. After creating a test script using Virtual User Generator, You Can parameterize the script. This operation allows you to test your application using several sets of actual data, this reflects the load capacity of the system. Taking an order input process as an example, a parameterized operation can replace fixed data in the record, such as the order number and customer name, with variable values. In these variables, enter the possible order number and customer name at will to match the operation behavior of multiple actual users. After Virtual users are created for real loads, you need to set your load scheme, business flow combinations, and the number of Virtual users. With LoadRunner's Controller, you can quickly organize testing solutions for multiple users. The Rendezvous function of Controller provides an interactive environment in which you can establish continuous and cyclic loads and manage and drive load testing solutions. In addition, you can use its Schedule service to define when users access the system to generate loads. In this way, you can automate the test process. You can also use Controller to limit your load scheme. All users in this scheme execute an action at the same time, such as logging on to an inventory application to simulate peak load. In addition, you can monitor the performance of each component in the system architecture, including servers, databases, and network devices, to help customers determine system configurations. Location performance LoadRunner contains an integrated real-time monitor. You can observe the running performance of the application system at any time during the load testing process. These performance monitors show you the real-time performance of transaction performance data (such as response time) and other system components, including application server, web server, network devices, and databases. In this way, you can evaluate the running performance of these system components from both the customer and server aspects during the test, so as to detect problems faster. Using LoadRunner's ContentCheck TM, you can determine whether the application function under the load is normal or not. When ContentCheck is running on Virtual users, it detects the network packet content of the application and determines whether any error content is transmitted. Its real-time browser helps you observe program performance from the perspective of end users. Once the analysis results are tested, LoadRunner collects and summarizes all the test data and provides advanced analysis and reporting tools to quickly locate performance problems and trace the cause. With LoadRunner's Web transaction details monitor, you can learn the time required to download all images, frames, and text to each Web page. For example, this transaction detail analysis mechanism can analyze whether the application system runs slowly due to a large size graphic file or a third-party data component. In addition, the Web transaction detail monitor breaks down the end-to-end Response Time on the client, network, and server to facilitate problem identification and locate components with real errors. For example, you can break down the network latency to determine the DNS resolution time, the time it takes to connect to the server or SSL authentication. By using the LoadRunner analysis tool, you can quickly find the location and cause of the error and make corresponding adjustments. Repeat load testing is a repetitive process. After an error occurs, you must perform another load test on your application in the same solution. Check whether your correction improves the running performance. LoadRunner fully supports EJB load testing. These Java-based components run on the application server and provide a wide range of application services. By testing these components, you can identify and solve possible problems early in application development. With LoadRunner, you can easily understand the system performance. Its Controller allows you to repeat the same test scheme as before the error modification. Its HTML-based report provides you with a benchmark required to compare performance results, to measure how much improvement is made within a period of time and ensure the application is successful. Since these reports are HTML-based texts, you can publish them on your company's intranet for easy access. In the next article, the editor will record an online article using LoadRunner & reg; To test the BEA middleware product and share with you how to use LoadRunner for actual performance testing. 4. the LoadRunner's Virtual user LoadRunner uses Virtual users to simulate the pressure on the business system. The virtual user works under the monitoring of a central controller station. When creating a test plan, the first thing to do is to create a virtual user to execute the script. LoadRunner provides Virtual User Generator to record or edit Virtual User scripts. Use Vugen to create A virtual user and execute script. select run Virtual User Generator: B. create a single protocol script, select the protocol type as "Tuxedo 7" c.enter the executable file name (simpapp.exe) of the tuxedoclient program in the pop-up window, and select "Record into Action" as Action. Click "OK" to start the script. vugenwill start simpapp.exe, as shown in. Enter WSNADDR AND THE STRING (Tuxedo is powerful !) Then, click TOUPPER and the TUXEDO server will output the string (tuxedo is powerful!) after completing the request !) Write to "Output string" and click "stop recording. D. Edit the Vuser script. All operations performed in C are recorded in a script file. The content of the operations is as follows and saved as the simpapp. The script content is as follows: # include "lrt. h" # include "replay. vdf" Actions (){ Lrt_tuxputenv("WSNADDR = // 172.22.32.25: 7110"); lr_think_time (3); tpresult_int = upper (upper); lower (); data_0 = lrt_tpalloc ("STRING", "", 1 ); lrt_strcpy (data_0, sbuf_1); data_1 = lrt_tpalloc ("STRING", "", 1); tpresult_int = lrt_tpcall ("TOUPPER", data_0, 0, & data_1, & olen, 0); lrt_abort_on_error (); lrt_tpfree (data_0); lrt_tpfree (data_1); lrt_tpterm (); return 0;} the rough function in the Code is the TUXEDO function provided by LoadRunner. Number of secondary packages. E. Click the "execute" button in the toolbar to execute the script we just recorded to ensure that the execution is correct. Use the Controller to schedule virtual user. select "Run Controller: B." from the menu. create a new Scenario and select the recorded script (simpapp). Click "OK" to bring up the Scenario scheduling interface. In "Quantity", enter 100 to use 100 virtual users. (The virtual user is associated with the purchased LICENSE.) C. Click "Edit Schedule" to Edit the pressure Schedule. D. Select "Runtime settings" for Runtime settings. In the Pacing settings, "Number of Iterations" is used to set the Number of Vusers to be executed; "Start new iteration" is used to set the time when the scheduler iterates to execute Vusers. "Think Time" is used to set the response Time and thinking Time of Vusers, so as to try to exert pressure like normal people. "Ignore think time" indicates ignoring the thinking time, which is ideal and generally not used. "As recorded" indicates the actual operation time during recording. "Multiply recorded think time by" indicates that Vusers has several times the actual recording time. Set Miscellaneous in "Miscellaneous", such as using processes or threads. For TUXEDO, it seems that only the process mode can be selected. E. Select "Start scenario" to Start the stress test scheduling. The execution result is as follows: the pressure time is 5 minutes 41 seconds, the number of Vusers is 100, the total number of Actions transactions completed is 5625, the average response time is 5.561 seconds, and the TPS is 17.8. [1] 5 components 1. VuGen (Virtual user generator)Used to capture end user business processes and create an automatic performance test script (also known as a virtual user script ). 2. Controller)Used to organize, drive, manage, and monitor load tests. 3. Load Generator)Used to generate loads by running Virtual users. 4. Analysis (analyzer)This helps you view, analyze, and compare performance results.