100 likes | 281 Views
M AKING M ULTICORE S YSTEMS P ERFORM !. Read IDC’s Insight Report (#211311) on www.exludus.com: Extreme Computing: eXludus Reinvents Job Scheduling and Promises Improved Multicore System Utilization. Published: March 28th, R. Walsh, S. Conway, E. Joseph. Throughput. {. Target Throughput.
E N D
MAKING MULTICORESYSTEMS PERFORM! • Read IDC’s Insight Report (#211311) on www.exludus.com: • Extreme Computing: eXludus Reinvents Job Scheduling and Promises Improved Multicore System Utilization. • Published: March 28th, R. Walsh, S. Conway, E. Joseph
Throughput { Target Throughput MultiCore Variability { Throughput Run Time Target Run Time { Optimal Throughput { Run Time Target Run Time Multi-Core Application Performance Predictability and Throughput Under normal operating conditions an application run time determines the throughput capacity of systems. But on multi-core processor systems applications tend to interfere randomly with one another causing an effective loss of capacity to sustain performance level expectations. Node-Level Capacity Management, as per Multi-Core Optimizer, is designed to eliminate job interference performance impacts and optimize throughput.
MCore Optimizer:Dynamic Operational Research Given aircraft fleet (processor cores) Given hubs to service (jobs) Find optimal flight schedule to carry most passengers (throughput)
MCore Optimizer:Resource Allocation Without MCore Optimizer With MCore Optimizer • No OS / Application Change • Real-time optimal job mix search • Prevents job interference • Blocks resource conflicts • ‘Learns’ job resources needed Memory Memory CPU CPU Time Throughput Gain Each color represents one of eleven jobs, white spaces represent unused resources.
Serial Processing (i.e. WLM) gives best service time response ratio but worst throughput! JOB “B” JOB “A” Concurrent Processing (i.e. OS fair share scheduler) gives best throughput but worst run time response ration… JOB “A” JOB “B” PE-BF Processing gives best throughput and best run time response ratio. JOB “A” A job on the wait Q can temporarily run while the “primary” job blocks JOB “B” MCore Optimizer:Pre-Emptible Backfilling
DB MCore Optimizer:Feedback Scheduling • Tracks job resource use • Provides WLM with resource expectations • Prevents job interference with resource expectations • Supports LSF, PBS Pro, Moab, Torque, Open PBS, SGE past run history user qsub A.sh past run history qsub -l “500MB,1cpu,300sec” A.sh MCore Optimizer this run data A.sh MCore Optimizer
RepliCatorVM:Scalable VM Provisioning Performance Re-provision a 3 GB VM image on 1,000 systems in 60 seconds on a 1 Gbit network!
benoit.marchand@exludus.com +1 514 885 1270 (cell) dale.geldart@exludus.com +1 514 227 8411 (direct) +1 514 409 6143 (cell)
Workload Mgr … Application A Application B Application C Virtualized Resource Allocation Layer Operating System MCore Optimizer: Software Architecture • Virtualization technology : jobs run in an encapsulated environment • Cooperating “SociallyResponsible” resource consumption • Aligns and synchronizes resource use across software layers • Transparent to OS, Workload Manager & Application • No single point of failure MCore Optimizer
Sampling Loses Control Cluster Capacity Management Limit