- The Controller is invoked using parameter values within files in the Windows OS folder (WINNT for Windows 2000 and WINDOWS for Windows XP). The Windows folder is used because LoadRunner is designed to have only one instance of Controller running at a time on a machine.
- To quickly switch among several applications, save a copy of LoadRunner's ini files after working on it within the Controller, then use Notepad to craft a batch file to copy application-specific versions of ini files before executing wlrun. An example of file copy actions for application XXX:
- copy %LRDir%/config/wlrun7-XXX.ini %LRDir%/wlrun7.ini copy %LRDir%/config/wlrun7-XXX.dft %LRDir%/wlrun7.dft
- copy %WinDir%/wlrun7-XXX.ini %WinDir%/wlrun7.ini copy %WinDir%/wlrun7-XXX.dft %WinDir%/wlrun7.dft
- In the
wlrun7.inifile file [output] section, MaxNumberOfOutputMessages= from 10000 to 100000 for long runs. This limits the number of output messages stored in the database.
- MaxOutputUIRowsToShow limits the amount of messages/errors (lines) displayed in the Controller's Output window.
- In the QTWeb.lrp file within the LoadRunner Program Files dat\protocols folder section [Vugen], add entry MaxThreadPerProcess=5 to limit the number of threads managed by each load generator mdrv.exe process.
wlrun5.iniand wlrun7.dftfiles updated whenever values are changed within the Controller.
- In the
- The blocks of actions taken by each Vuser are
- defined in Vu scripts created using Loadrunner's VuGen.exe. When this program is invoked, it stores in the Windows folder a comparamui.INI file to save under "[LastTablesUsed]" a history of files and [ParamDialogDates] specified using menu option Insert > New Parameter > Dates. VuGen stores and retrieves a vugen.ini file in the Windows folder. When using Java, enable additional debug options:
- [DynaDlg] JavaLevel=3
- [Editor] OLDEDITOR = 1
Vu scripts can be coded to use variable values obtained from parameter files external to the script.
I have a lot more on VuGen here
- During a run, execution results are stored to a results folder.
- I prefer to set Results Settings to "Automatically create a results directory for each scenario execution." which means that LR will increment the name of the Results Name when I start a scenario runs. For example, a value of "Res11" will be automatically incremented to "Res12" or sometimes "Res11-1".
- Within each results folder, a "Log" folder is automatically created to contain a log file for each group. After a run, to view a log file from within the Controller, click then right-click on a group to select "Show Vuser Log".
- As a scenario is run, monitors maintain counters locally on each host.
- After a run, the "collate" process takes .eve and .lrr result files and creates in the results folder a temporary .mdb (MS-Access) database. To prevent errors when processing large result files, use MSDE (Microsoft SQL Desktop Engine).
- setup SAPWD="StrongPassword" INSTANCENAME="LR" SECURITYMODE=SQL DISABLENETWORKPROTOCOLS=0 /L*v path to log file
Then in Analysis Options > Database tab, use 8.3 names without spaces (indentified with DOS command DIR /X):
- Input the SAPWD password specified above.
- Logical Storage location: \\loadclient02\Data (the folder you shared)
- Physical Storage Location: C:\PROGRA~1\MICROS~1\MSSQL\Data (not C:\Program Files\Microsoft SQL Server\MSSQL\Data)
- Click "Test parameters". (This takes a few seconds)
- The Analysis Module (8,320K analysisu.exe)
- generates analysis graphs and reports using data from the .mdb database.
- The LoadRunner Results file results_name.lrr from each scenario run -- also called an Analysis document file -- is read by the Analysis program to display Percentile graphs.
- By default, the LRReport folder is created in the test analyst's local machine My Documents folder to store Analysis Session files.
- They can optionally be formated in HTML.
- Their format are controlled by a .tem template file.
- Optionally, Mercury's Remote Performance Monitoring (RPM) MS-IIS/ASP web server for LoadRunner 7.8 can be installed on a Windows 2000 server ( but not on a Windows 2003 server) so that
- load test results to be viewed using a web browser.