...
- Job:
run_parallel_jobs
- This job makes use of the following parameters:
- Parameter
job
:- Purpose: the name or path of the test job to execute. Modify this value to point to the job
parallel_job_unix
if you are running the test suite in a Unix environment. - Default:
parallel_job_windows
- Purpose: the name or path of the test job to execute. Modify this value to point to the job
- Parameter
sleep
- Purpose: the number of seconds that the test job should execute.
- Default:
10
- Parameter
tasks
- Purpose: the number of parallel tasks.
- Default:
50
- Parameter
- This job makes use of the following parameters:
- Job:
parallel_job_windows
,parallel_job_unix
- Optional configuration items:
- Option Options
tasks
- Purpose: this option specifies the max. number of tasks that this job can be executed for. Tasks that exceed this number will be enqueued.
- Default:
500
- Option Options
- Optional configuration items:
- Process Class: Performance
- Optional configuration items:
- Attribute:
max_processes
- Purpose: the max. number of tasks that can be executed for all jobs that are assigned this process class. Tasks that exceed this number will be enqueued.
- Default:
100
- Attribute:
- Optional configuration items:
...
- If your overall system performance slows down then you have hit the limit of parallelization. This might occur at 100, 200, 500 or more tasks in parallel.
- You can verify the performance impact from the duration of individual tasks that are available in with the JOC tasks history or by use of JID.
- The estimated duration of a task is the number of seconds specified for the
sleep
parameter plus about 1s for the task start. - If the duration of a task exceeds the value of the
sleep
parameter by more than e.g. 3s then you experience some performance impact. - When you experience missing responsiveness of your operating system then the performance impact has become inacceptable.
- The estimated duration of a task is the number of seconds specified for the
...