camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Riccardo Sirchia (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-5828) Offer LMAX Disruptor pattern as an endpoint in CAMEL
Date Mon, 20 May 2013 23:05:16 GMT

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

Riccardo Sirchia updated CAMEL-5828:
------------------------------------

    Attachment: camel-disruptor.patch

This patch contains everything required to add a new Camel disruptor and disruptor-vm component
(in one bundle). If preferred over a patch file, a pull request by the name of 'CAMEL-5828
- Added camel-disruptor component' is also offered on Github.com.

I've got some documentation (in line with the SEDA Camel component) ready prepared. Please
let me know how and in what format it should be offered to be included on the Camel website.

I hope it can be included in Camel 2.12. Please let me know if there is anything that needs
correction/improvement.
                
> 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
>             Fix For: Future
>
>         Attachments: camel-disruptor.patch
>
>
> 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

Mime
View raw message