job management option (wlm) scalability tests r11 december 12 2005 -

Job ManagementOption (WLM)

Scalability Tests r11December 12 2005

-

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Objectives

- The main objective is to run basic scalability tests with Unicenter Job Management Option r11

- Define 7500 Job sets in a suite of 75.- Each suite has 100 jobsets- Each jobset has 6 jobs

- Job 1 – No dependency- Job 2 – No dependency - Job 3 – No dependency- Job 4 – Dependent on completion of Jobs 1,2 and 3- Job 5 – Dependent on Job 4- Job 6 – Dependent on Job 5

- Each jobset with the exception of the first jobset, is dependent on the previous jobset- Each job will execute cawto.exe command- Maximum of 45,000 jobs to be scheduled each working day- NO dependency between Job Suites. All 75 Job suite will run at the same time

- Perform tests on Windows Operating System


Job Suite & Jobset Structures

JobSet 1

JobSet 1

JobSet 2

JobSet 100

Job Suite JobSet

Job 1 Job 2 Job 3

Job 4

Job 5

Job 6


Machine Specification


Agent Breakdown

- JMO – Manager- Total Jobset 7500- Total Jobs 45,000

- Agents- Local Server (Same server as where Manager is running)

- 3000 Jobsets- 18,000 Jobs

- Remote Server- 4500 Jobset- 27,000 Jobs


Tracking File Cleanup

1400 Jobsets

8400 Jobs

Purged in 78 seconds


Adding Schedule Jobsets to Tracking File

Adding Jobset to Tracking File:

1400Jobsets - 15 seconds

7500 Jobsets – 77 seconds

First Jobset Last Jobset


Adding Schedule Jobs to Tracking File

First JobLast Job

Adding Jobs to the tracking file

8400 Jobs - 188 seconds

45000 jobs - 1116 seconds (18mins)


Counts


Monitor Status


Classic Gui


Total Scheduling Time – 8400 Jobs

Last Job

Last Jobset19 mins 43 seconds to complete 8400 jobs including job submission, execution time and dependency delays


Total Scheduling Time – 45000 Jobs

Start of First Job End of Last

Jobset

161 mins 9 seconds to complete 45000 jobs including job submission, execution time and dependency delays


Scheduling Overhead

This shows time it took from completion of a job to execution of next dependent job

7 seconds


Scheduling Overhead – Peak Time

This shows time it took from completion of a job to execution of next dependent job

14 seconds

In this test, there can be 75 job suites active. Each Job suite can have 3 jobs active at one time. Maximum number of job completion events that can be generated is 225.


MCC Displays


MCC User Interface

- There was significant delay in MCC “Job Status” display. MCC displays in small chunks of around 60 jobs but the count varied and took significant time. It would not be practical to administer 45,000 jobs with MCC UI.

- Class Gui (caugui tjob) took around 20 seconds to display and sort 45,000 jobs


Conclusion

- MDB = Ingres

- 45000 jobs with reasonable number of dependency can be executed without significant delay.

- There will be some delay in administrator of these of jobs from some User Interfaces.

- Autoscan time has been significantly improved


Questions??

- Mail to:

- Yatin Dawada- [email protected]

- Bill Merrow

- [email protected]

job management option (wlm) scalability tests r11 december 12 2005 -

Documents

trade names

services marks

respective companies

dependency job

job suites

previous jobseteach

seconds45000 jobs

completion of jobs