html5-img
1 / 18

Job Management Option (WLM) r11 Basic Scalability Tests

Job Management Option (WLM) r11 Basic Scalability Tests. Objectives. Primary Objective: 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

lita
Download Presentation

Job Management Option (WLM) r11 Basic Scalability Tests

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Job ManagementOption (WLM)r11 Basic Scalability Tests

  2. Objectives • Primary Objective: 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

  3. JobSet 1 JobSet 1 JobSet 2 JobSet 100 Job Suite & Jobset Structures Job Suite JobSet Job 1 Job 2 Job 3 Job 4 Job 5 Job 6

  4. Machine Specification

  5. 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

  6. Tracking File Cleanup 1400 Jobsets 8400 Jobs Purged in 78 seconds

  7. Adding Jobsets to Tracking File Last Jobset First Jobset Adding Jobsets to Tracking File: 1400 Jobsets - 15 seconds 7500 Jobsets – 77 seconds

  8. Adding Jobs to Tracking File First Job Last Job Adding Jobs to the tracking file 8400 Jobs - 188 seconds 45000 Jobs - 1116 seconds (18 minutes)

  9. Counts

  10. Monitor Status

  11. Classic GUI

  12. Total Scheduling Time – 8400 Jobs Last Job Last Jobset 19 mins 43 seconds to complete 8400 jobs including job submission, execution time and dependency delays

  13. 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

  14. Scheduling Overhead Time lapse between completion of one job to execution of next dependent job 7 seconds

  15. Scheduling Overhead – Peak Time 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. Time lapse between completion of one job and execution of the next dependent job 14 seconds

  16. MCC Displays

  17. MCC User Interface • There was a significant delay in MCC “Job Status” display. MCC displays data in small chunks of around 60 jobs but the count varied and took significant time. This suggests it would not be practical to administer 45,000 jobs with MCC UI. • Classic GUI (caugui tjob) took approx. 20 seconds to display and sort 45,000 jobs – Better Approach!

  18. Conclusion • MDB = Ingres • 45,000 jobs with reasonable degree of dependency can be executed without significant delay. • However, there will be some delay in administrating these of jobs from some User Interfaces. • Autoscan time has been significantly improved from previous release

More Related