Mainframe Migration - 8
Transaction Rate Ratio (measured)
Response Time (90th percentile)
Transaction Rate Ratio (extrapolated)
The above table indicates the effect of keeping the transaction rate relatively fixed while varying the number of CPUs in the configuration. In the two tables above, a 2-CPU case is included for comparison purposes and represents an off-the-shelf machine. Although capable of running the mainframe migration workload, it is evident these smaller systems use more CPU to process the same amount of transactions making them less efficient than “enterprise class” machines This is likely due to a limited I/O subsystem. The differences between the configurations show that a 16-CPU configuration is about 8x the speed of a 2-CPU configuration. The difference between 8 and 16-CPU configurations show a 1.9x performance advantage. Differences in the 12-CPU configuration may have led to the less than 50 percent improvement over the 8-CPU configuration. Further analysis of performance logs is required.
This paper has shown that continued improvements in CPU and disk subsystem design continue to improve upon the ability of Windows based systems to run mainframe workloads at high rates. An 8-CPU enterprise-class system is capable of 1715 MIPS of mainframe processing. Better than 80 percent of existing mainframe IT data centers are at or below this size. We feel comfortable predicting that any CICS COBOL transaction workload that can fit in mainframes of this size or smaller could be migrated to the architecture discussed here.
From the scalability tests we can conclude that Windows Server 2003 Datacenter Edition SP1 together with Micro Focus Enterprise Server with the Mainframe Transaction Option scales in a close-to-linear fashion for varying numbers of CPUs in the multiprocessor CPU configuration, having tested 12- and 16-CPU configurations. Evidence indicates that high-performance “enterprise-class” processing systems with adequate memory, high bandwidth to disk subsystems allow COBOL CICS transactions to execute effectively when moved off the mainframe.
WinHEC 2005 Version - April 20, 2005