1 tools-options -- settings related to loadgenerator behavior apply to all load generators in a scene
These settings are used for all future runs of the scenario and usually only need to be set once
2 expert mode--provides access to system information, the controller dialog contains additional fine-tuning options
3 Runtime files - exist by default under the temporary files of each load generator. You can set the runtime files to be stored on a network shared drive with read and write permissions for the controller and load generator, tools/options/runtime file storage
Runtime file type:
1 vuser script files: When running a vuser, the controller sends a copy of the relevant user script to the load machine, which exists in the temporary running directory of the load machine
If you specify that all virtual users access the script directly from a shared address, without transferring the script file at runtime, this approach usually requires path translation.
This approach applies to the following situations:
1 The file transfer device does not work;
2 The user script file is too large and takes a long time to transfer, (only once in a scene)
2 result files: When running a scenario, the participating vusers write the running results to the temporary running file directory, the scenario execution is completed, these result files are collected from all load machines and transferred to the result address, and the result files are collected - temporary running time file is deleted
Note: 1 The loadrunner applies these settings to all participating loaders in a scene, and can change the settings of individual loaders
2 It is not recommended to store files in a shared address, as this will increase network traffic and require a path change.
path translation: used when the remote computer has a different name for the same path
If both the controller and the load machine are Windows machines, consider using a uniform naming convention so that all machines know the path without the need for path translation
tool-options-execution post collate command: command to be executed after collecting scene results
tool-options-run time file storage: Specify where to save the file for the scene to run on the remote load machine
debug information tab: expert mode
Check keep temporary files to instruct the agent and controller not to delete temporary files
The agent files are saved in the brr folder under temp, and the controller files are saved in the lrr folder
options-run time file storage tab
on the current vuser machine: save the runtime file to the load machine running the script,
Need to collect results: 1 Open profiler - wait for loadrunner to collect
2 results-collate resullts
3 results-auto collate results
on a shared network drive