# Editing Concurrency and Timeout Factor

To change the concurrency and the timeout factor in the template, perform the following steps:

1. Choose View > Quick Set Mode from the Template Editor menu bar.
2. Click the Execution tab in the Template Editor.

3. Change the values in the Concurrency and Time Factor fields as required.
   See Concurrency and Time Factor for detailed descriptions of these settings.

4. Change additional template settings or click the Done button to save the changes in the template.
   If you are creating a new template for these changes, instead of clicking the Done button, choose File > Save As from the Template Editor menu bar and save the template with a relevant name.

## Concurrency

The harness can run tests concurrently. If users run tests on a multiprocessor computer or are using multiple agents on a test system, concurrency can reduce the time required to run tests. For detailed information about using agents to run tests, refer to the test suite documentation and to the JT Harness Agent User's Guide if it is provided by the test suite.

When using multiple agents to run tests, the concurrency value must not exceed the number of agents. If the concurrency value exceeds the total number of available agents, an error will occur in the test run.

The default range of values used by the harness is from `1` to `50`. If unexpected test failures occur, run the tests again, one at a time. Some test suites may not work correctly if tests run concurrently.

For the first test run, set the value in this field to `1`. After the tests run properly, incrementally increase this value. Unless the test suite restricts concurrency, the maximum number of threads specified by the `concurrency` command is `50`. See the test suite documentation for additional information about using concurrency values greater than `1`.

This field is disabled for some test suites.

## Time Factor

To prevent a stalled test from stopping a test run, most test suites set a timeout limit for each test. The timeout limit is the amount of time that the harness waits for a test to complete before moving on to the next test.

If users run tests on a slow CPU or slow network, change the time limit by specifying a floating point value in the time factor field. Each test's timeout limit is multiplied by the time factor value. The default range of values used by the harness is from `0.1` to `100.0`.

In the Time Factor field, the harness uses the form of floating point values that is specific to the locale in which it is run. For example, if your locale uses floating point values in the form of `x,x`, harness uses that form of floating point value in the Time Factor field. In setting the timeout factor in the following example, specify values of `2,0` and `0,5` if your locale uses floating point values in the form of `x,x`.

Example:

If you specify a value of `2.0`, the timeout limit for tests with a basic 10-minute time limit becomes 20 minutes. Specifying a value of `0.5` for tests with a 10-minute limit produces a 5-minute timeout limit.

At first, use the default value of `1.0` to run tests and then, if necessary, increase the value. The actual timeout calculation for any particular test suite might vary.

Copyright © 2006, 2010, Oracle and/or its affiliates. All rights reserved.