This Blog Has Moved!

Right, so yes, five years ago I moved to github pages, and never bothered to redirect any of these pages there. Now I've moved on from there, and... Finally I am using my real domain, trishagee.com . My blog is now at trishagee.com/blog .  See you there!
Post a Comment

Strangeloop Disruptor Workshop Materials

On Sunday I gave my very first workshop on the Disruptor.  The aim was to give people some hands-on coding experience using the syntax.  Because time was limited (you can't get people to build an entire application architecture in 2.5 hours) the example is somewhat contrived, and needs a big leap to make it into a proper application context.  But the workshop should:
  1. Give an overview of the Disruptor
  2. Show how to create a simple one producer, one consumer example.
  3. Show how to wire up a parallel event handler
  4. Show how to how (and why) to create a diamond dependency graph.
  5. Extrapolate beyond these very simple examples to something closer to a real world architecture.
Requirements are:
  1. Basic Java skills
  2. Java 7 update 7
  3. (Optionally) IntelliJ.
The slides (not all that useful, I'll grant you, without me talking) are available, and you can download the code.

If you want to work through the examples yourself, start with com.mechanitis.towerdefense.TowerDefence.  The starting point code for the workshop is in package com.mechanitis.towerdefense.  com.mechanitis.towerdefense1 shows a solution to exercise one, com.mechanitis.towerdefense2 to exercise 2 and so forth.  The final package, com.mechanitis.towerdefense4, has some different towers you can play with to see the effects.  They don't really show anything special about the Disruptor, but they were fun to write and are interesting to play with.






Comments

  1. Andrew Luetgers27 September 2012 at 03:39

    Trisha - the session was great, the materials and information were superb!

    ReplyDelete
  2. Anonymous3 March 2013 at 11:02

    Hi Trisha:

    Thank you for this perfect demo! I see it now much clearer, how Disruptor can be used! I believe this was missing in the official Disruptor pages.

    I still have two questions:

    1. I don't understand the usecases for complex pipelines. Could you bring perhaps one more situation where it makes sense to have more than the typical Consumers (Persister/Logger, Business Logic, Outgoing Socket) and the typical Producers (Business Logic, Incoming Socket). I thought long and did come up with one pattern where it may make sense: Say we need to calculate orderbooks for 100 symbols, and the orderbook calculation logic takes quite a long time. Then I have the sockets that give me new quotes; and they are then consumed by two orderbook-restoration consumers. And then the business logic (for example calculate a few indicators based on the status of the orderbooks) runs only after the two orderbook consumers have finished. In this case one orderbook-consumer would be configured to process only symbols starting A-M and the second orderbook-consumer would only process symbols starting N-Z. Any other possible uses for complex
    pipelines?

    2. Complexity of Data-class in ringbuffer.

    For my example above, then the data-class used inside the ring-buffer will get more and more complex; and I am not sure if this is what should be the case.

    Also if the ring-buffer is only used as a replacement for a queue, then
    the data class will not be optimal. Typically I can imagine that the data
    class would be say a enum DataType{Trade=1, Quote=2, TradingSignal=3}, then
    the data itselv would be in a "object DataLink" which I imagine introduces
    a lot more garbage.

    Did I get the point of this issue? Or am I clueless?

    3. Threading of Producer and Consumer:
    Producers need to manage their own threading; and Consumers run in their
    own thread; BUT the managent of this thread is managed by the Disruptor.
    Now for Producers I may only use one thread, correct? So if I have one
    Thread for each incoming socket, then I need to have as many producers as
    sockets?

    Thank you
    Florian




    If for example the sockets





    For this reason I would have two order





    ReplyDelete

Post a Comment

Comments have been disabled since this blog is no longer active.

Popular posts from this blog

Dissecting the Disruptor: What's so special about a ring buffer?

Image
Recently we open sourced the LMAX Disruptor , the key to what makes our exchange so fast.  Why did we open source it?  Well, we've realised that conventional wisdom around high performance programming is... a bit wrong. We've come up with a better, faster way to share data between threads, and it would be selfish not to share it with the world.  Plus it makes us look dead clever. On the site you can download a technical article explaining what the Disruptor is and why it's so clever and fast.  I even get a writing credit on it, which is gratifying when all I really did is insert commas and re-phrase sentences I didn't understand. However I find the whole thing a bit much to digest all at once, so I'm going to explain it in smaller pieces, as suits my  NADD audience. First up - the ring buffer.  Initially I was under the impression the Disruptor was just the ring buffer.  But I've come to realise that while this data structure is at the heart of the patte
Read more

Dissecting the Disruptor: Writing to the ring buffer

Image
This is the missing piece in the end-to-end view of the Disruptor.  Brace yourselves, it's quite long.  But I decided to keep it in a single blog so you could have the context in one place. The important areas are: not wrapping the ring; informing the consumers; batching for producers; and how multiple producers work. ProducerBarriers The Disruptor code has interfaces and helper classes for the Consumer s, but there's no interface for your producer, the thing that writes to the ring buffer.  That's because nothing else needs to access your producer, only you need to know about it.  However, like the consuming side, a ProducerBarrier is created by the ring buffer and your producer will use this to write to it. Writing to the ring buffer involves a two-phase commit.  First, your producer has to claim the next slot on the buffer.  Then, when the producer has finished writing to the slot, it will call commit on the ProducerBarrier . So let's look at the first bi
Read more

Dissecting the Disruptor: How do I read from the ring buffer?

Image
The next in the series of understanding the Disruptor pattern developed at LMAX . After the last post we all understand ring buffers and how awesome they are.  Unfortunately for you, I have not said anything about how to actually populate them or read from them when you're using the Disruptor. ConsumerBarriers and Consumers I'm going to approach this slightly backwards, because it's probably easier to understand in the long run.  Assuming that some magic has populated it: how do you read something from the ring buffer? (OK, I'm starting to regret using Paint/ Gimp .  Although it's an excellent excuse to purchase a graphics tablet if I do continue down this road.  Also UML gurus are probably cursing my name right now.) Your Consumer is the thread that wants to get something off the buffer.  It has access to a ConsumerBarrier , which is created by the RingBuffer and interacts with it on behalf of the Consumer .  While the ring buffer obviously needs a se
Read more