How to access and modify the BENCHMARK_TIMEOUT_MULT variable when troubleshooting benchmark errors
In the course of testing with BAPCo benchmarks, users sometimes experience a timeout error. Timeout errors are usually attributed to the following causes:
- The SUT’s battery charge is depleted, and the SUT is throttling performance to extend battery life.
- The SUT is a lower performing configuration, and therefore may take longer to perform some benchmark tasks
If timeout errors occur, users may wish to adjust the BENCHMARK_TIMEOUT_MULT environment variable to extend the timeout before a benchmark error is registered. Please refer to the attached screenshot for guidance on modifying the BENCHMARK_TIMEOUT_MULT variable. After modifying the variable, the SUT must be rebooted for the new setting to take effect.