SUSE Linux Enterprise Real Time. Carl Drisko, Linux & Open Source Principal

Transcription

1 SUSE Linux Enterprise Real Time Carl Drisko, Linux & Open Source Principal

2 Customer Results with Real Time 2 Business Results A large investment bank has said that for every 1 millisecond their algorithmic applications can beat the market, they would earn an additional $100 Million per year! Another major Investment Bank is seeing trades execute 30% to 300% faster for a time-critical algorithmic trading application. Performance and Server Consolidation Results UMB Bank has seen performance improvements ranging between 10% to 150%+ under heavy loads for their enterprise Identity Management solution while decreasing their overall physical server footprint by 75% A very large global bank requires 1/5 th the number of market data servers to meet stringent performance SLAs.

3 Customer Success UMB Bank By deploying SUSE Linux Enterprise Real Time, UMB's server infrastructure is able to deliver significantly better performance (greater than 10% under light load and over 150% under heavy load) for our enterprise Identity Management solution while decreasing our overall physical server footprint by 75%. Scott Wiles, AVP/Manager, Distributed System, UMB n.a. Business Issues: Novell Solution: Results: Identify critical jobs and assign them dedicated resources (processor, memory, interrupts, etc.) Decrease server footprint in their Data Center Novell Identity Manager SUSE Linux Enterprise Real Time Performance increases between 10% under light load and over 150% under heavy load Decreased the number of servers from 8 Sun Solaris non-real time servers to 2 real time servers for UMB's Identity Manager 3 implementation a 75% reduction 3

4 SUSE Linux Enterprise Real Time Double's Wombat Feed Handler Capacity to 200,000 message per second Customer Benefit 2x through-put improvement for Wombat Server 1 Wombat Feed Handler 4 Consumer Application Connections Subscribing to 100,000 Symbols Each 50,000/second per connection Voltaire 9096 Switch 4 Server 2 Wombat Client 2 Consumer Applications/Client Handling A Total Of 200,000 msgs/sec Server 3 Wombat Client Partner Components Intel WoodCrest Chips Voltaire

5 SUSE Linux Enterprise Real Time Outperforms Red Hat 275 Ingres Database Performance Time In Seconds RHEL4 SLERT Threads Generating System Load 5 Partner Testing on AMD

6 Oracle 10g TPC-C Benchmark Maximum Response Time Time (s) SLES SLE RT User Load 6

7 Live Comparison at a Major Investment Bank 550 Archipelago Data Using The Flood Test th Percentile Latency Implication Flood Test 550 Inet RHEL4 SLERT 7

8 What is SUSE Linux Enterprise Real Time? An add-on to SUSE Linux Enterprise Server providing deterministic performance in time-critical environments. An industry-standard real-time version of Linux for x86 architectures engineered providing the following key features: CPU Shielding: Dedicated resources (such as CPU, memory, fabric) for high priority processes Kernel Preemption: Fast response to external events, optimized kernel critical sections (aggressive lock breaking) Priority Inheritance: Solves priority inversion problem for mission critical processes 8

9 What's the secret? Standard Linux Kernel Measured 44,759,417 samples Max latency: 92.3 millisecs samples < 0.1ms (99.140%) samples < 0.2ms (99.630%) samples < 1.0ms (99.843%) samples < 10.ms (99.939%) samples < 30.ms (99.975%) samples < 60.ms (99.999%) 166 samples < 90.ms (99.999%) 1 sample < 100ms (100%) Interrupts fire at 490 us /dev/rtc 9 September 08, 2005 Novell Inc, Confidential & Proprietary Kernel with Real-time Extensions Measured 28,800,882 samples Max latency: 27 microsecs Min latency: 11 microsecs Average latency: 11.3 microsecs 28,808,870 samples < 0.02 ms ( %) 12 samples < 0.03 ms (100%)

10 CPU Shielding: The Processing Highway The way CPU Shielding improves processing can most easily be understood by the analogy of cars running on a highway. Associate: CPU/Core --> Lane, Process/Thread --> Car Interrupt --> Truck, Consumed CPU time --> Distance While this analogy is not strict, it illustrates many effects of Shielding: Shielding of CPUs/Cores from other processes and interrupts is pictured in the upper lane The advantage of shielding is less apparent when there is little load ( = traffic on highway) Even at times of very low traffic, there is no guarantee that no truck will show up. Workloads with few high-priority Processes/Threads benefit most from Shielding. 10

11 When Is Real-Time The Appropriate Platform? Use standard kernel for throughput sensitive workloads and realtime kernel for latency sensitive workloads (for example): Standard Kernel: Real Time Kernel Throughput Sensitive Workloads When fair scheduling algorithms are required across compute resources (time sharing) Web farms serving FIFO based requests Enterprise mail servers Systems running multiple workloads Latency Sensitive Workloads Limited number of threads or clear priority hierarchy Market data feeds (Wombat, Tibco, Reuters) Algorithmic Trading: Minimize time from receipt of new market information to recalculation of risk and trade execution Applications requiring faster, predictable data delivery predictable, low data latency (e.g., Home Banking applications) 11 High volume Online Transaction Processing Applications (e.g. ATM transactions, credit card authorizations, etc.)

12 Questions and Answers

13