2. Why?

3. Data storage applications (caches,
queues, databases, etc) implemented
in Ruby suffer two major problems

4. You cannot use
multiple CPU
cores

5. Pausing GC
causes serious
delays for large
data sets

6. What does
Arabesque
Promise?

7.  Scalability to multiple CPU
cores
 Constant performance profile
regardless of queue size
 Can be used stand alone or
embedded

8. Secret Sauce?

9. Berkeley DB

10.  Single writer multiple reader concurrency
in a multi-process or multi-threaded
environment
 Data is stored in a shared memory area
away from Ruby's GC
 Master-slave data replication
 Create data structure exclusively in
memory

11. Benchmarks

12. Multi CPU Scaling
Single Process Dual Processes
0
2000
4000
6000
8000
10000
12000
14000
16000
18000
20000
Number of Processes
Operations/Sec

13. GC Time
Zero 100K 1M 10M
0.00%
2.00%
4.00%
6.00%
8.00%
10.00%
12.00%
Queue Size
%ofGCTimetoapplicationtime

14. Deployment Options

15. In-Process Library

16. Pros
 Very fast
 Much easier to setup and use
 Less moving parts
Cons
 Does not scale to multiple physical
servers
 If you do that you lose ordering (might
not be an issue)

17. Standalone Server

18. Pros
 Allows multiple front end servers to use
the same queue
 Allows the queue to scale up or scale out
independently from the front end
Cons
 More moving parts
 Added latencies of TCP/HTTP
communication overhead
 Loses strict queue ordering in scale out
scenarios

19. Thank You!