disruptor-pattern

I'm not providing full listing as below code is enough for those who familar with disruptor. The question is if calling Next and Publish methods is thread-safe. Between examples below what would be the correct one? Note that Attach can be called from different threads at the same time. And I have multiple consumers. Example1. Lock everything: private object attachLock = new object(); // can be called from parallel threads public void Attach(OrdersExecutor oe) { lock (attachLock) { long sequenceNo = ringBuffer.Next(); ringBuffer[sequenceNo].Value = oe; ringBuffer.Publish(sequenceNo); } }

I want to learn the Disruptor framework . Who can give me a helloworld example which can run in the main method with Java program language? Trevor Bernard Here is a simple, runnable, example of how to use the Disruptor library. Example is written using version 2.10.4 of the Disruptor library. https://github.com/trevorbernard/disruptor-examples I've also cross posted on this thread: The simplest and actual example code of LMAX Disruptor Here One more from my side. I tried one disruptor example using open source Lmax libraries. I think idea behind the use of lmax disruptor (not the internals of

I was curious regarding the most common (or recommended) implementations of disruptor about the journaling step. And the most common questions of mine are: how it is actually implemented (by example)? Is it wise to use JPA? What DB is commonly used (by the community that has already implement projects with disruptor)? Is it wise to be used at the intermediate handlers (of EventProcessors) so the State of each message should be saved, rather than before and after the business logic process? By the way (I am sorry, I know this is not related with the journalling step), what is the right way to

While using the disruptor, there may be a consumer(s) that is lagging behind, and because of that slow consumer, the whole application is affected. Keeping in mind that every producer(Publisher) and consumer(EventProcessor) is running on a single thread each, what can be the solution to the slow consumer problem? Can we use multiple threads on a single consumer? If not, what is a better alternative? Generally speaking use a WorkerPool to allow multiple pooled worker threads to work on a single consumer, which is good if you have tasks that are independent and of a potentially variable duration

I wish I can get the simplest possible example code, which will show how to use LMAX disruptor(http://code.google.com/p/disruptor/). Unfortunately every piece of code is out of date. Does someone know, where can I found small and up to date howto (preferable without DSL)? you can see the example here. http://code.google.com/p/disruptor/wiki/CodeExampleDisruptor2x I have done a simple example by using the above wiki. hope this helps you. Here is a simple, runnable, example of how to use the Disruptor library. Example is written in Java using version 2.10.4 of the Disruptor library. https:/

Disruptor github address is: https://github.com/LMAX-Exchange/disruptor I've a simple test for it as below: public class DisruptorMain { @SuppressWarnings({ "rawtypes", "unchecked" }) public static void main(String[] args) throws Exception { class Element { private int value; public int get() { return value; } public void set(int value) { this.value = value; } } ThreadFactory threadFactory = new ThreadFactory() { @Override public Thread newThread(Runnable r) { return new Thread(r, "simpleThread"); } }; EventFactory<Element> factory = new EventFactory<Element>() { @Override public Element