Share this page

# Runtime file storage locations

This topic describes how to store runtime files on a shared network.

In this topic:

## About runtime files storage

When you run a scenario, by default the runtime files are stored locally on each load generator (the machine running the Vuser script). The default location of the files is in the temporary folder specified by the load generator's environment variables (on Windows, TEMP or TMP, and on Linux, $TMPDIR or $TMP). If no environment variable is defined, the files are saved to the /tmp folder.

Alternatively, you can store the runtime files on a shared network.

You select where to store runtime files in the Runtime File Storage tab.

## Shared network

A shared network location is a folder or drive to which Controller and all the load generators in the scenario have read and write permission. If all Vusers access their Vuser scripts directly at some shared location, no transfer of script files occurs at runtime. This method may be useful in either of the following situations:

- The file transfer facility does not work.
- The Vuser script files are large and therefore take a long time to transfer.

Note: Keep in mind that Vuser script files are transferred only once during a scenario, and using a shared network drive will increase network traffic.

Using a shared network location may necessitate path translation. Path translation ensures that all participating machines recognize the same network drive. For examples, see Path translation.

Where possible, we recommend using the same shared network drive mapping for Controller and all load generator machines, to avoid the need to define path translation.

How to work with a shared network location:

1. Make sure the scenario scripts are all stored in a shared network location.
2. Create a results folder at a shared network location. This can be at the same shared location as the scripts, or in a different shared location. Define the path in the Result Settings dialog box.
3. If path translation is required for the shared locations, enter the necessary information in the Path translation table.
4. To configure global use of the shared network location for the scenario, open theTools > Options > Runtime File Storage tab and select Shared Network Drive. Alternatively, define this individually for each load generator running the scenario, in the load generator configuration Runtime File Storage tab. For details, see Load Generator Configuration > Runtime File Storage tab.

## Runtime file types

The primary runtime files are as follows:

Runtime File Type | Description
--- | ---
Vuser Script files | When you run a Vuser, Controller sends a copy of the associated Vuser script to the load generator. The script is stored in the load generator's temporary runtime folder. If you use a shared network location, no transfer of script files occurs at runtime.
Result files | While you run a scenario, the participating Vusers write their results to the temporary runtime file folder. After scenario execution, these result files are collated or consolidated—results from all of the load generators are transferred to the results folder. After collating the results, the temporary runtime folder is deleted. If you use a shared network location, all results from all load generators are written to the shared results folder.

## See also

- Run a scenario

- Prepare a scenario to run

- Collate scenario run results

https://admhelp.microfocus.com Professional Performance Engineering,VuGen 8942
Tips to improve your search results... OpenText™ Professional Performance Engineering Help Center OpenText™ Professional Performance Engineering Help 26.1-26.3 All View Local Help Center View Online Help Center Version: