Apresentação realizada no evento de premiação do Concurso Mainframe 2014 que foi realizado em São Paulo, IBM Tutóia. Tópicos apresentados incluíram: hardware System zEC12 e zBC12, Linux on z, O que o System z faz que outras plataformas não fazem e um caso real de uma empresa desenvolvedora de Software.
Central Processor
zSeries Application Assist Processor
zSeries Integrated Information Processor
Integrated Facility for Linux
Coupling Facility
System Assist Processor
A side by side comparison that shows the dramatic difference in the abilities of System z to maintain high priority workload SLAs. ESX is unable to handle both high priority and low priority workloads without a huge adverse effect on the high priority work.
The net result: wasted CPU.
The only ESX solution that maintains the high priority SLAs requires segregating the high priority work into serves that are high priority workloads only.
Intel/VMware is not able to maintain the SLA of the high priority workload when lower priority workload is added
Severe throughput and response time degradation
With Intel/VMware, the only practical solution to maintain SLAs of high priority workloads is to deploy workloads into separate environments
For example, most Intel/VMware deployments separate Dev environments from Production environments
The need to maintain multiple environments directly affects the total cost of the solution
Fixed size Intel boxes can force additional boxes to support “spill over” high priority work
There may be spare capacity on the additional machine, but nothing else can run on it without impacting the primary workload’s SLA
Additional environment needed to deliver lower priority workloads