SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Scalability Testing of Unicenter Job Management Option r11 (December 2005)

zwi avatar
zwi
19 diapositives · 311 Views · Oct 20, 2014

This document outlines the objectives and findings from basic scalability tests conducted with Unicenter Job Management Option r11. The tests defined 7,500 job sets across 75 suites, totaling 45,000 jobs processed daily. Each job suite consists of dependent and independent jobs executed on a Windows system. Key metrics include scheduling times, job execution delays, and interface responsiveness. The results indicate that while the system can handle the job load efficiently, delays in user interface performance were noted, impacting job administration.

Scalability Testing of Unicenter Job Management Option r11 (December 2005) - slide 1
01 / 19Scalability Testing of Unicenter Job Management Option r11 (December 2005)
1 / 17

Télécharger la présentation

Scalability Testing of Unicenter Job Management Option r11 (December 2005)
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. Job ManagementOption (WLM)Scalability Tests r11December 12 2005

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

  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 Schedule Jobsets to Tracking File Last Jobset First Jobset Adding Jobset to Tracking File: 1400Jobsets - 15 seconds 7500 Jobsets – 77 seconds

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

  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 This shows time it took from completion of a 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. This shows time it took from completion of a job to execution of next dependent job 14 seconds

  16. MCC Displays

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

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

  19. Questions?? • Mail to: • Yatin Dawada • Yatin.Dawada@ca.com • Bill Merrow • Bill.Merrow@ca.com