Solace Systems The Evolution of Messaging The Rise of the Appliance
27
The Evolution of Messaging The Rise of the Appliance Clive Andrews Mat Hobbis
-
Upload
iosif-itkin -
Category
Documents
-
view
217 -
download
5
description
Solace Systems The Evolution of Messaging The Rise of the Appliance Clive Andrews Mat Hobbis Obninsk, 2 March, 2013 LSE The focus beyond Low Latency EXTENT Trading Technology Trends & Quality Assurance
Transcript of Solace Systems The Evolution of Messaging The Rise of the Appliance
The Evolution of Messaging
The Rise of the Appliance
Clive AndrewsMat Hobbis
Adoption Cycles
Functionality& Performance
Time
Adoption Cycles
Functionality& Performance
Time
Considerations in Selecting
Hardware vs. Software
Hardware: Extreme Performance
Hardware: Predictable Behavior
Hardware: Massive Scale
Hardware: 24x7x365 Reliability
Hardware: Cost
Software: Versatility
Hardware Products are Widely Available and Simple to Deploy
Softwareon Servers
EnterpriseAppliances
o Easier Operation
o Lower TCO
o Higher Performance
DatabaseStorageWebInfrastructure
MessagingMiddleware
IPRouting
Applying the Appliance Advantage to Middleware
Don’t Make Headlines
“India stock exchange flash crash erasesUS$58 Billion”October 2012
“IT leaders face pay cut after TSE outage”August 2012
“Facebook crashes the Nasdaq”December 2012
Application Evolution
15CONFIDENTIAL
16CONFIDENTIAL
Event Driven Architecture (i)• Need to be Agile.• Increased Regulation . Audit, “Real-Time” Global Risk and P&L• Drive EDA for scale and resilience – drives message bus requirements• Bus Latencies and Throughput important
Trade Bus Trade Bus
Monitor /Staging Bus Monitor / Staging Bus
OMSSub
Post TradeDist Svc
DBPersist
OMSSub
Post TradeDist Svc
DBPersist
Risk P&L
17CONFIDENIAL
Event Driven Architecture (ii)• Co-Locate Processes where Latency is
key• Shared Memory IPC within host (Same
API)• Non “on host” components also need
Low Latency Connections.• Lower Latency requirements of
Staging area allow message batching– Turn Message Rate problem into a
Bandwidth Problem
• Need High Availability and recovery options
• Need Disaster Recovery options
Trade Bus
OMSSub
Post TradeDist Svc
DBPersist
CrossingEngine SOR
Physical Host
Shm Q
Product Architecture
18CONFIDENTIAL
19CONFIDENTIAL
Networked Architecture• Hardware-based middleware overlay for IP networks• All Message QoS in one Appliance – Reliable/Persistent/Web
Streaming• WAN Optimisation and Compression• Comprehensive Statistics and Monitoring
20CONFIDENTIAL
Modular Addition of Functionality
Data Plane Capabilities embedded in FPGAs and network processors, added via modular architecture
- Build to suit
- Scale within footprint
- Easy upgrades
Control Plane Administration, subscriptions and stats collection never impact performance
High-Speed Interconnect
(10 blades in 3260,5 blades in 3230)
Solace Blades(PCIe Cards)
Reliable Messaging• Pure hardware solution
– No operating system– No context switching– No interrupts– No data copies
• 10 million messages/second– Can be any combination, e.g.
5M in & 5M out, 2M in & 8M out
21CONFIDENTIAL
500K/500K 1M/1M 2M/2M 3M/3M 4M/4M 5M/5M0
10
20
30
40
50
60
22 23 24 2629
3525 2630
32
39
54Avg
99.9th
Messages per Second
Micro-seconds
of La-tency
BulkMessage
Rate
Message Size(bytes)
Message Rate (msgs/sec)
User PayloadBandwidth (Mbps)
100 5,930,000 4,744
500 2,080,000 8,320
10GigE Line Rate is the Limit
1,000 1,080,000 8,640
12,000 92,000 8,832
30,000 34,000 8,160
CONFIDENTIAL
Guaranteed Messaging; Store & Forward Performance
Failsafe w/o overhead of persisting every message to disk
200K msgs/sec ingress and 200K msgs/sec egress
Latency steady even while recovering when disconnected subscribers reconnect
22
2,000 10,000 25,000 50,000 100,000 125,000 150,0000
20
40
60
80
100
120
140
160
180
69 69 69 7379 84
98
90 88 9199
114123
154Avg
99.9th
Messages per Second
Micro-seconds
of La-tency
500 1,000 2,000 4,0000
50,000
100,000
150,000
200,000206,400 202,000
157,500
124,400
ADB-3 Software Broker
Msg
Rat
e (M
sg/s
ce)
ADB Message Rates
Guaranteed Messaging;Cut Through Persistence Latency
23CONFIDENTIAL
Low, consistent latency for low latency trading applications
Can also have store & forward clients for same published message
Queues can have low and high priority limits set.
During congestion :
Reject new orders
Process changes to existing orders
Steady in Face of Slow Consumerso Latency stays consistent
even through disconnection and re-connection of clients
oRe-connected subscribers “catch up” without impacting other clients
Pre-Failure Spooling Catchup/Recovery Post-Recovery0
20406080
100120140160180
74 7589
74
103 113
170
103
Avg99.9th
Period of Test
Micro-sec-onds of La-
tency
24CONFIDENTIAL
IPC Shared Memory Messaging• Single API session for:
– Communications between processeson one OS instance
– Topic-based pub/sub and request/reply
– Any-to-any messaging
– Reliable delivery
• Applications can block or busy-wait
• C API for Linux, Solaris and Windows
• Move apps to IPC with no application changes
25CONFIDENTIAL
Core1
Core3
Core2
Core4
SharedMemory
1 publisher -> 1 subscriber• 2.91 million msgs/sec; 128 byte messages• Average latency 431 nanoseconds
99th percentile 480 nanoseconds
6x6 mesh simulation of fanout/fanin• 46.8 million messages per second• 154.5 gigabits per second
Thanks……
