loadrunner培训知识文档.ppt

Instructor will explain all the aspects of the interface Introduce the point that while ignoring think time in replay generates a higher load on back end, it may not be the best way to test (to avoid LR people thinking it’s a way to avoid buying a higher license key.) General tab is mostly administrative. Transactions measure the time required by a business process, and most load testing goals are measured against their performance. Because one transaction usually relies on a different set of components and tiers than another, the relative performances of various transactions suggests a picture of those components performance. But transaction timings alone are not conclusive enough to pinpoint a bottleneck. What else is needed? For remote performance monitors provides custom views Each user can create custom views for the monitors. This is a new feature in LR 7.6 SA- See above- Picture of the Per mon stats with lots of things to look at as the virtual users execute their scripts, a whole team is needed to maximize the usefulness of the test. Backend administrators should monitor the performance of each tier of the Web application. One or more network administrators should monitor the network as load increases. By using the third-party performance monitoring tools already in place, these administrators will complement the LoadRunner LoadTest results and enhance the efficiency of the root cause analysis process First, the scenario is executed with a just one or a few Vusers. This debug execution shows the responsiveness of the site under low stress and validates that BP function for concurrent usage with the data being used in the test. Debug run is also know as concurrency test basically at this point we are testing if more than Vuser can be run concurrently from the controller. Once the concurrency is established run 20% of load to isolate transactions that are the slowest. The objective here is to find if there are any bottlenecks.This helps in understandin