You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2013/06/03 18:17:23 UTC

[jira] [Resolved] (CAMEL-5828) Offer LMAX Disruptor pattern as an endpoint in CAMEL

     [ https://issues.apache.org/jira/browse/CAMEL-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang resolved CAMEL-5828.
---------------------------------

    Resolution: Fixed

Updated the [wiki page|https://cwiki.apache.org/confluence/display/CAMEL/Disruptor].

                
> Offer LMAX Disruptor pattern as an endpoint in CAMEL
> ----------------------------------------------------
>
>                 Key: CAMEL-5828
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5828
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Eric
>            Assignee: Willem Jiang
>             Fix For: 2.12.0
>
>         Attachments: came-disruptor.incremental.patch, camel-disruptor.patch, fixDisruptorUnitOfWorkTest.patch, README.md
>
>
> My system is an hybrid of CAMEL and LMAX Disruptor, where threads consuming from LMAX ringbuffer are feeding a "pool" of SEDA queues in a round-robin fashion.  This system operates at very high-speed such as consumers from the SEDA queues and their producers are constantly blocking on the queues.  Having a non-blocking, high-performance endpoint like LMAX Disruptor would be a great addition to CAMEL.
> LMAX Disruptor website: http://lmax-exchange.github.com/disruptor/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira