Modifying Load Test Logging Settings
The load test result for the completed load test contains performance counter samples and error information that was collected in a log periodically from the computers-under-test. A large number of performance counter samples can be collected over the course of a load test run. The amount of performance data that is collected depends on the length of the run, the sampling interval, the number of computers under test, and the number of counters to collect. For a large load test, the amount of performance data that is collected can easily be several gigabytes; therefore, you might consider modifying how often data is saved to the log. For more information, see Distributing Load Test Runs Across Multiple Test Machines Using Test Controllers and Test Agents.
The test controller spools all collected load test sample data to a database log while the test is running. Additional data, such as timing details and error details, is loaded into the database when the test completes.
Note
For a complete list of the run settings properties and their descriptions, see Load Test Run Settings Properties.
Requirements
- Visual Studio Ultimate
Task |
Associated topics |
|---|---|
Specify how frequently to save logs during a load test run: You can specify how frequently you want the test log saved when your load test is run. |
|
Save logs if a load test fails: You can specify if you want to save the test log whenever a load test fails. |
|
Set the maximum file size for the log file: You can edit the XML configuration file that is associated with the test controller service to specify the maximum file size you want to use for the log file. |
Related Tasks
A related property is Timing Details Storage. For more information, see How to: Configure Load Tests to Collect Full Details to Enable Virtual User Activity in Test Results.