Reserving Test Server Processes
Using reserved processes as part of your test session increases performance and data throughput by allowing you to run tests across multiple threads/processes on a single Test Server. When using the Port Reservation feature, if you have multiple Groups of Test Case using the same PHYs, you may assign each Group to a particular TS virtual process. This will let you have more control over the balance of performance across your test.
NOTE: When you reserve processes to run your test session, the Performance Accelerator features, that increase the Test Server capacity, data, and performance throughput, are used if your system is licensed. To take full advantage of the accelerators you need to reserve at least three processes and set up your test case to port relationship correctly. That is, setup a test session with three test cases each configured using different ports. Reserving processes allows your test request multiple processes, and is allocated only if they are available (i.e., in PA mode and no other test is already using them). A Test Server in Performance Accelerator mode runs 3 instances of the test server (3 processes). Executing your test session with reserved processes allows you to use multiple processes on each test server (i.e., if PA mode is selected and available). |
NOTE: Selecting Reserve Processes for assignments of virtual processes automatically selects Port Reservation, which must be done after you have reserved ports and before running/saving a test.
|
Assigning Virtual Processes:
Select the test session and before executing it, select the Session Builder tab..., click the Reserve Processes checkbox, and then click the Assign button.
A TS Virtual Process Assignments window opens. The window displays a separate tab for each TS with a list of processes, related Groups of Test Cases, and ports assigned. In default mode (No checkboxes enabled, the TC-Groups will be round robin assigned to a logical Process based on the Target # of Processes. The Target # or Processes = MAX would make the #processes the lowest of either the 'number of TC-Groups' or the 'max TS-processes supported by the License'. If fewer processes than specified in this dialog are available on the TS when the test is executed, the test will run with the TC-Groups round-robin assigned by the TAS to make them fit. See additional options below.
|
IMPORTANT: The processes, groups of TC instances and PHYs displayed when the Enable Custom Assignments check box is not selected, does not reflect the automatic assignment by the TAS. The window displays the optimum assignment which would be used when you select the Enable Custom Assignments check box. |
Select the Prevent test from running with fewer processes check box to prevent the test from running when not enough processes are available.
When the check box is not selected, let the Test can run with fewer than the requested number of processes.Select the Enable Custom Assignments check box to modify the automatic assignments of processes by TAS and/or assign all test cases on one process. For Custom Assignments, you are choosing how many processes you need and which TC-Groups are running together/separate on those processes. The Target # of Processes (see below) is only used to let you have enough processes to choose from, ultimately the # of processes you are requesting is determined by the process indexes you choose in the table. When you run in this mode and check [x] Prevent test from running with fewer processes, the TAS will not allow the test to run if there are not enough available processes to match your custom assignment, regardless of the Target # of Processes Combo Box.
When the check box is not selected, the TAS will assign the TC-Groups on a round robin basis. Select when you want to assign the TC-Groups to processes by your own custom groupings, other than the default Round-Robin. Example : You may want one TC-Group by itself and the remaining can share the same process.Click Put all test cases on one process to assign all test cases on one process.
Click Use exact TS Processes and the Process Column will be renamed TS-Process to allow you to pick any absolutely TS-Process Index. They no longer must start at zero (0) and are not just relative, but correlate to the exact TS-Process on the TS .
Select the Target # of Processes - When choosing MAX, you are letting the TAS make sure that you get all of the processes currently initialized by the Test Server (TS). If the TS has a standard amount of processes (1), or if the TS has 3 and your test has 3 or more TC-Groups, then it’s 3. In this setting you will only be prevented from running your test, if someone else is using one of the processes on the TS, NOT if the TS does not have enough processes license/running. By choosing a specific 0-4 as Target # of Processes and checking [X] Prevent test from running with fewer processes, the TAS will not allow the test to run if there are not enough processes ‘available’. By choosing MAX as Target # of Processes in Automatic and check [X] Prevent test from running with fewer processes, the TAS will not allow the test to run if you do not get enough processes up to the # of provided processes on the TS. For example, it will not fail if you run on a TS with only 2 processes, but you have 4 processes assigned, instead it will automatically reduce and assign to 2.
Select the Test Server Tab to modify.
You may modify the Process ID assigned to the Group ID of the Test Cases instances and the allocated Physical Interfaces and override the automatic assignment by TAS.
NOTES:
|