HP OpenVMS Alpha and Integrity Performance Comparison

Transcription

1 HP OpenVMS Alpha and Integrity Performance Comparison Session 1225 Gregory Jordan OpenVMS Engineering Hewlett-Packard 25 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice

2 Overview The purpose of this presentation is to provide the appropriate expectations of the performance of OpenVMS on Integrity platforms vs. Alpha platforms The performance of various Integrity platforms will be compared with a variety of current Alpha platforms.

3 Integrity/Alpha Performance Comparison The Basics Processors Integer and Floating Point Memory Latency and Bandwidth IO Fibre Channel, Lan OpenVMS Performance Various OS Components Improvements in V8.2-1 Applications Improvement Stories Conclusions

4 CPU Integer test program Integer Computations Rating (single CPU) rx GHz/3mb rx26 1.5GHz/6MB rx GHz/4mb ES45 1GHz GS GHz More is better

5 SETI Time to Process a Work Unit CPU Seconds Less is better rx26 1.5GHz rx26 1.3GHz DS25 1GHz XP 1 666MHz

6 Processor Comparison The Itanium processors are fast. The current Itanium processors are faster than current Alpha processors Various SPEC benchmarks also show the Itanium processors outperforming Alpha processors

7 Memory Latency (small servers) Computed via memory test program Latency (ns) rx GHz/3MB rx26 1.5GHz/6MB rx GHz/4MB ES45 1GHz Less is better

8 Memory Latency (large servers) Computed via memory test program Latency (ns) rx GHz/4MB Superdome 1.5GHz 1 Cell Superdome 1.5GHz 2 Cell Superdome 1.5GHz 4 Cell GS GHz Less is better (Superdome memory is interleaved between cells)

9 Memory Bandwidth (small servers) Computed via memory test program MEMSpeed Test Program MB/sec rx GHz/3MB rx26 1.5GHz/6MB rx Ghz/4MB ES45 1GHz More is better

10 Memory Bandwidth (large servers) Computed via memory test program MEMSpeed Test Program MB/sec rx GHz/4MB SuperDome 1.5GHz 1 Cell SuperDome 1.5GHz 2 Cells SuperDome 1.5GHz 4 Cells GS GHz More is better

11 Memory Comparison Alpha Servers have very good memory latency Applications that read small amounts of data from many different memory locations should perform well The small Integrity Servers have very good memory bandwidth Applications which move memory around or heavily use caches or RAMdisks should perform well The large Alpha Server have very good memory latency and good memory bandwidth

12 IO MB/Sec single process (QLogic ISP2313) 2Gigabit Fiber Channel Card - EVA-GL Random Read/Write 12 1 MB/Sec ES45 1GHz rx GHz 1 Block 4 Block 8 Block 16 Block 32 Block 64 Block More is better 128 Block 256 Block

13 CPU per IO single process (QLogic ISP2313) 2Gigabit Fiber Channel Card - EVA-GL Random Read/Write Block 4 Block 8 Block 16 Block ES45 1GHz rx GHz usec CPU/IO 32 Block 64 Block 128 Block 256 Block Less is better

14 Gigabit Transmit MBytes/Sec rx GHZ (A6825A - Broadcom 571) in 64-bit 66 mhz DS25 1GHz (DEGXA - Broadcom 573) in 64-bit 66 mhz MB/sec DS25 1GHz rx GHz More is better

15 Gigabit Transmit CPU Utilization rx GHZ (A6825A - Broadcom 571) in 64-bit 66 mhz DS25 1GHz (DEGXA - Broadcom 573) in 64-bit 66 mhz 1% CPU Utilization 8% 6% 4% 2% DS25 1GHz rx GHz % Less is better

16 IO Conclusions IO appears comparable between Alpha and Integrity Servers Both Integrity and Alpha can driver IO adapters at comparable levels CPU cost per IO appears better on Integrity servers We don t have IO Stress tests from Superdome class systems at this point

17 Lock Manager Stress Test Converts/sec (1s) 4 Processes Active CPUs More is better rx GHz rx GHz ES45 1GHz GS GHz

18 Lock Manager Stress Test V8.2 compared to V Processes Converts/sec (1s) Active CPUs More is better rx GHz V8.2 rx GHz V8.2-1

19 XFC Cached 1 Block IOs Cached IOs/sec 18, 16, 14, 12, 1, 8, 6, 4, 2, Processes More is better rx GHz GS GHz ES4 833MHz

20 XFC Cached 4 Block IOs Cached IOs/sec 18, 16, 14, 12, 1, 8, 6, 4, 2, Processes More is better rx GHz GS GHz ES4 833MHz

21 XFC Cached 16 Block IOs Cached IOs/sec 18, 16, 14, 12, 1, 8, 6, 4, 2, Processes More is better rx GHz GS GHz ES4 833MHz

22 Performance Improvements in V8.2-1 SWIS Improvements Reduced overhead System Service Dispatching $SETSTK_64 implemented as an EPC service Alignment Fault fixes Macro32, LBRSHR, LIB$MATCH_COND, LCKMGR DEC$BASRTL (in V8.2 Tima)

23 RMS1 (Ramdisk) Direct IOs 6 IOs per second GS GHz Superdome 1 Cell 1.5GHz Superdome 2 Cells 1.5GHz Superdome 4 Cells 1.5GHz rx GHz Processes More is better

24 RMS1 (Ramdisk) MP Synch IOs per second Processes Less is better GS GHz Superdome 1 Cell 1.5GHz Superdome 2 Cells 1.5GHz Superdome 4 Cells 1.5GHz rx GHz

25 RMS1 (Ramdisk) V8.2 compared to V8.2-1 IOs per second Processes More is better rx GHz V8.2 rx GHz V8.2-1

26 Oracle RDB Performance Comparison ES Ghz rx Ghz 4 2 H Records Per Second Loading Transactions Per Second 3 process OLTP workload

27 Areas that are Slower on Integrity There are several areas where the equivalent operations on Integrity systems are slower Alignment Faults! Exception Handling! Establishing/Finding Exception Handlers takes longer Exceptions Frames much larger VAX Floating Point Data Types (due to conversions) Did you compile /NOOPTIMIZE? Integrity Images are typically 3 times as large This can impact image activation time Requires more IO Increased page faults Require larger GH regions if images are installed resident Requires more disk space for listings and object files

28 Macro Compiler Story Macro Compiler Customer had a regression test suite of 7 batch jobs Spent most of the time compiling Macro32 code Alpha 1 (244MHz CPUs) Total CPU Time: 5:29:23 Total Elapsed Time: 22:17:7 IPF system: rx26 dual 1.4GHz CPUs Total CPU Time 1:26:17 Total Elapsed Time: 21:54:41 PC Sampling revealed very heavy alignment faults About 1 fixes were made to avoid the alignment faults IPF system: rx26 dual 1.4GHz CPUs Total CPU Time 1:46:21 Total Elapsed Time: 7:7:49

29 Application Signaling Story Recent testing of an application on Integrity showed very poor performance There was very heavy CPU usage compared to Alpha PC sampling showed the problem to be with establishing condition handlers These condition handlers were very short lived The code contained calls to the old CMA library routines to perform mutex and condition variable operations The TRY/CATCH_ALL/ENDTRY macros were necessary to catch error statuses the CMA routines did not directly return status codes Solution: call pthreads directly and the condition handling setup is no longer required

30 OS Update Story An HP field person was testing a small program on Integrity for a large financial institution In order for the customer to move to Integrity in the next 6-9 months, this test had to perform well The test took twice as long and used twice the CPU on integrity when compared to Alpha Analysis showed very heavy memory allocation and deallocation on Integrity that did not appear on Alpha The OS code in question used KP services to create contexts to execute each transaction This was a porting change since usage of stack context is much more involved on Integrity than on Alpha An update was made to cache the data structures and provided back to the HP field person for testing The test program now run faster in both elapsed time and CPU usage on Integrity than on Alpha

31 Projected Performance Crossover Point predicted three years ago OpenVMS on Processor Performance EV7 EV7z

32 Conclusions

33 Conclusions hardware The Itanium Processors are fast Future processors will continue to increase the performance over current alpha processors IO performance is also comparable between Alpha and Integrity Integrity has an edge in CPU cost per IO and in cached and DECram IO The rx464 and rx26xx systems have great memory bandwidth and good memory latency In most cases, these systems should perform similar or better to comparable Alpha systems The larger Integrity servers have slower memory latency If your application taxes a large GS128, we recommend testing on larger Integrity servers before moving performance critical applications

34 Conclusions - software The OpenVMS operating system performs well on Integrity servers with just a few caveats Alignment faults and exception handling OpenVMS V8.2-1 shows performance improvements over V8.2 Additional Integrity Server improvements can continue to be expected in the next release of OpenVMS We expect most applications to perform well on Integrity servers If you port an application and are disappointed in performance we want to know Please contact me with performance issues at: Gregory.Jordan@hp.com