Scaling Your Test Session

You can use a combination of options to scale testing intensity to meet your diagnostic needs. For example, you can modify test options so that each test instance runs simultaneously, thus increasing the stress level for a single or multiprocessor system. The following procedures can be used individually or in combination to scale the test session.

To Modify the Number of Test Instances

You can scale your test session by running multiple copies of the same test on your devices. Each copy is called a test instance. Each test instance is a separate process of the same test. The number of test instances can be set at the system level, group level, and the device level as follows:

1. Open the Test_Execution Option menu at one of the following levels:

   • System-level--select Test_Execution from the set_options menu in the Control panel.

   • Group-level--select Test_Execution from Options next to the group in the Test_Groups panel.

   • Device-level--select Test_Execution from the device in the device option menu.

2. Highlight the Num of Instances setting, and enter the value you want.

3. Highlight Apply, and press return.

To Modify Test Concurrency Options

The test concurrency option sets the number of tests that run at a given time during a test session. You can set this value to one to run one test at a time, or increase the test concurrency value thus increasing the stress level of your test session.

There are two options you can modify in the Schedule Option dialog boxes (at the system level and group level) to scale your test session:

• System Concurrency--sets the maximum number of tests that run simultaneously at the system level. It overrides the Group Concurrency option.

• Group Concurrency--sets the maximum number of tests that run simultaneously in the same group.This option is available at the system level and the group level.

1. Open the Schedule Option menu at one of the following levels:

   • System-level--select Schedule from the set_options menu in the Control panel.

   • Group-level--select Schedule from Options next to the group in the Test_Groups panel.

2. Highlight the concurrency setting, and enter the value you want.

3. Highlight Apply, and press return.

To Bind a Test to a Processor with the Processor Affinity Option (for Multiprocessor Systems)

By default, the Solaris kernel assigns each test instance to whichever processor is available at the time. On multiprocessor systems, you can bind (assign) a test instance to a particular processor as follows:

1. Open the Test_Execution Option menu at one of the following levels:

   • System-level--select Test_Execution from the set_options menu in the Control panel.

   • Group-level--select Test_Execution from Options next to the group in the Test_Groups panel.

   • Device-level--select Test_Execution from the device in the device option menu.

   ---

   Note -

   The Processor Affinity field is only displayed on multiprocessor systems.

   ---

   ---

   Note -

   The Processor Affinity option is not available for processor tests such as cputest and fputest. These tests are associated with each individual processor on your system and you cannot bind these tests to a different processor.

   ---

2. Highlight the Processor Affinity setting, and enter the value you want.

3. Highlight Apply, and press return.