LoadRunner的工作原理图.docVIP

LoadRunner的工作原理图 1,777 Views 下面一个是LoadRunner的工作原理图,更多的LoadRunner的理论请参考: /1loadrun.htmwilson先生对LoadRunner有比较透彻的研究,这可以从他的分析中看出. 这张是LoadRunner的总体架构图,包括各个组件VUGen, Controller和Analysis之间的关系. 这是LoadRunner的工作原理,从图中可以看出如何利用LoadRunner进行一次典型的系统性能测试 这是一个内部流程图,LoadRunner内部各个组件之间如何进行交互,数据流和文件流之间如何进行. 下面是各个步骤的简单介绍: 1. application serverson this page under test are placed under stress by2. driver processes mdrv.exe (the Multi-threaded Driver Process) and r3vuser.exe which emulate application clients such as Internet Explorer web brower. It performs 3 main actions:(1). Kli cpp (C language pre-processor) cci (C pre-compiling) which creaes a file with ci file, and(2). execute using the driver for the protocol technology being tested. Runs can be invoked to run “silently” by invoking Mdrv.exe from a Windows batch script. Mdrv can automatically stop loading Vusers because they communicate with Vusers and monitor CPU usage on Windows Load Generator machines. A separate JVM is instantiated by each Java-based Vuser on Windows-based machines. #Java Vusers are not supported on Unix platforms. 3. virtual Vusers are invoked as groups (logical collection of virtual users running the same script on a specific load generator machine)4. by agents (3,900K magentproc.exe) running as a service or as a processon this page5. on load generator client machines. 6. Each machine hosting agents maintains an Execution Log in a .qtp file.7. When logging is enabled, the agent also creates within the results folder a sequential log file for each Vuser (segregated by Vuser group).8. During execution, this file is displayed in the view Show Output window on the LoadRunner Controller machine. 9. Upon a pre-set delay, the Scheduler running on a Controller machine instructs agents (via Windows port 54345 or dynamic Unix port) to initiate test session scenarios. The Controller (wlrun.exe) sends a copy of scenario files along with the request.10. Agents are launched by the Remote Agent Dispatcher process