Download as PDF, PPTX
Uploaded byTrisha Gee
Workshop: Introduction to the Disruptor
The document provides an introduction to the LMAX Disruptor, a data structure for high performance inter-thread messaging. It describes the Disruptor as allowing very fast message passing without contention by using a lock-free data structure called a ring buffer. The workshop covers the basic components of the Disruptor including the publisher, event handlers, and batch processing. It includes exercises to demonstrate wiring up a simple Disruptor configuration, adding parallel event handlers, and managing dependencies between handlers. Real-world uses like high throughput financial applications are also discussed.
More Related Content
Similar to Workshop: Introduction to the Disruptor
Workshop: Introduction to the Disruptor
- 1. An Introduction tothe LMAX Disruptor Trisha Gee, Developer at LMAX Exchange @trisha_gee mechanitis.blogspot.com Tuesday, 25 September 12
- 2. Laptop Setup... Go! Tuesday,25 September 12
- 3. The Disruptor? Tuesday, 25September 12
- 4. The Workshop • Introduction to the Disruptor • Simplest Case • Performance Results • Going Parallel • The Real World • Questions Tuesday, 25 September 12
- 5. What is TheDisruptor? • Very fast message passing • Data structure and work flow without contention • Allows you to go truly parallel Tuesday, 25 September 12
- 6.
- 7. The Magic RingBuffer Tuesday,25 September 12
- 8. The Magic RingBuffer Tuesday,25 September 12
- 9. The Magic RingBuffer Tuesday,25 September 12
- 10. The Magic RingBuffer Tuesday,25 September 12
- 11. The Magic RingBuffer Tuesday,25 September 12
- 12. The Magic RingBuffer Tuesday,25 September 12
- 13. The Events areBuckets Tuesday, 25 September 12
- 14. I’ve got aRingBuffer! • Erm.... how do I poke things into it? Tuesday, 25 September 12
- 15. The Publisher Tuesday, 25September 12
- 16.
- 17.
- 18.
- 19.
- 20.
- 21.
- 22. ...so now Iwant to read • The Disruptor provides nice batching behaviour for free Tuesday, 25 September 12
- 23.
- 24.
- 25.
- 26.
- 27.
- 28.
- 29.
- 30.
- 31.
- 32.
- 33.
- 34.
- 35.
- 36.
- 37.
- 38. The Problem Tuesday, 25September 12
- 39. Tower Defence? Tuesday, 25September 12
- 40.
- 41.
- 42.
- 43.
- 44.
- 45. Exercise One One publisher, one event handler Tuesday, 25 September 12
- 46. Our Problem Tuesday, 25September 12
- 47. Simplest Disruptor Tuesday, 25September 12
- 48. TODO • Print status of the enemy when the tower sees it • Print status of enemy after the tower shoots it • Shoot all enemies Tuesday, 25 September 12
- 49. Task Breakdown • Wire up the EventTranslator & EventHandler, using the Disruptor class • Implement shootAt • Implement respawn & isDead • Get unit tests to pass • (check out mechanitis.examples.disruptor) Tuesday, 25 September 12
- 50. Exercise One Goals 1. Understand the roles of Translators and Event Handlers 2. Understand how to wire up a simple Disruptor configuration 3. Understand how to get events flowing through the Disruptor Tuesday, 25 September 12
- 51. Performance vs a Queue Mac Air, 1.7GHz Core i5: run 0: BlockingQueue=3,390,060 Disruptor=69,108,500 ops/sec run 1: BlockingQueue=5,229,851 Disruptor=71,123,755 ops/sec run 2: BlockingQueue=4,303,481 Disruptor=65,530,799 ops/sec Disruptor - Time Taken: 3,242 millis Disruptor - Time Taken: 3,319 millis Disruptor - Time Taken: 4,045 millis Queue - Time Taken: 30,022 millis Queue - Time Taken: 31,823 millis Queue - Time Taken: 29,280 millis Tuesday, 25 September 12
- 52. Exercise Two One publisher, two parallel event handlers Tuesday, 25 September 12
- 53. Let’s log allthe enemies Tuesday, 25 September 12
- 54. Parallel Processors Tuesday, 25September 12
- 55. • Make eachenemy unique • Write the details of each enemy generated into a text file Tuesday, 25 September 12
- 56. Task Breakdown • Add randomness to enemy (e.g. give them a speed to travel at) • Wire in the EnemyLogger • Implement describeTo in enemy Tuesday, 25 September 12
- 57. Exercise Two Goals 1. Understand that EventHandlers can process in parallel 2. Understand how to wire up EventHandlers in parallel 3. Understand the caveats to going parallel - single writer principal Tuesday, 25 September 12
- 58. Exercise Three Diamond Dependencies Tuesday, 25 September 12
- 59. Recording the Results Tuesday,25 September 12
- 60. Sequence Barriers Tuesday, 25September 12
- 61. Managing Dependencies Tuesday, 25September 12
- 62. • Don’t usethe Disruptor Wizard for configuration • Record results of the game to a different text file • Optional: add variability to Turret Tuesday, 25 September 12
- 63. Task Breakdown • Remove use of Disruptor.java and wire up manually (mechanitis.examples.disruptor) • Wire in ResultHandler • Add missing things from Enemy class Tuesday, 25 September 12
- 64. Exercise Three Goals 1. Understand sequence barriers 2. Understand different dependency configurations 3. Understand wiring up without the wizard Tuesday, 25 September 12
- 65. Exercise Four Playtime!! Tuesday, 25 September 12
- 66. Slow Consumers? Tuesday, 25September 12
- 67. The Real World Tuesday,25 September 12
- 68.
- 69.
- 70.
- 71. Ticket Purchasing Tuesday, 25September 12
- 72.
- 73.
- 74.
- 75.
- 76.
- 77.
- 78.
- 79. Other Uses • Queue replacement • Single-threading your code • Filtering • Coalescing • Dependency graphs Tuesday, 25 September 12
- 80.