JS7 JobScheduler

Space shortcuts

Page tree

Introduction

The purpose of performance tests is to know the limits of a given hardware/software environment.

Depending on the product in use different tests are performed:

  • Controller & Agent
    • The maximum parallelism of job executions that will not cause delays or slowness on a given machine.
    • SOS runs performance tests for 28 million job executions in 24 hours. This is not what everybody needs.
    • For most users performance tests are intended to identify if available performance meets their needs.
  • JOC Cockpit
    • The maximum number of parallel user sessions that allows timely responses from the GUI.

The JS7 has no built-in limits. However, performance relies on assignment of resources such as CPU and memory. The result of a performance test is not a statement about JS7 performance, it's a statement about applicable load for a given hardware and software environment.

Users might underestimate performance requirements: for example when normal job load suggests parallelism of 100 jobs while after maintenance windows or after longer outages the job load can drastically increase when late orders scheduled for a point in time during the maintenance window or outage will start immediately and in parallel. The JS7 Agent will not crack under pressure. However, users should be aware of their hardware/software system's limits and should prepare for such a situation. If a given machine is overloaded, then this will create delays in the range of multiples of normal duration for job execution.

Test cases are available for download from the JS7 - Self-Test article.

Test Metrics

Metrics include that any performance tests are run in iterations.

  • Each next iteration doubles the load.
  • Time is measured for execution of test cases per iteration and is compared for evaluation purposes.

Test Runs

Find details how to run performance tests from the following articles:

Test Result Evaluation

Test cases typically will raise errors if problems occur. This does not apply to delays in test case execution, that are subject to user's evaluation.

  • After test execution, users can check the JS7 - Order History for failed orders. 
  • Job errors invalidate test results. A successful test case includes that any orders related to the test case are completed successfully.

Resources

Pages

 
 

Navigation


  • No labels