cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5582) Replace CustomHsHaServer with better optimized solution based on LMAX Disruptor
Date Tue, 21 May 2013 02:25:16 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662597#comment-13662597
] 

Vijay commented on CASSANDRA-5582:
----------------------------------

{quote}
My understanding was that Disruptor really wants to manage the whole lifecycle, e.g. Thrift
-> SP -> MS
{quote}
I think that will happen after we commit CASSANDRA-5239, Since we can have a ListenableFuture
which will change the intrest in thrift/netty etc. 

What i noticed is that, Disruptor in Stages will be a bad idea since it spins through the
Buffers and takes a lot of CPU cycles without any big advantage... I am sure Pavel will be
able to give more details or differ :)

BTW: i am going to run the test again in few min!
                
> Replace CustomHsHaServer with better optimized solution based on LMAX Disruptor
> -------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-5582
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5582
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API, Core
>            Reporter: Pavel Yaskevich
>            Assignee: Pavel Yaskevich
>             Fix For: 2.0
>
>         Attachments: CASSANDRA-5582.patch, disruptor-3.0.0.beta3.jar, disruptor-thrift-0.1-SNAPSHOT.jar,
Pavel's Patch.rtf
>
>
> I have been working on https://github.com/xedin/disruptor_thrift_server and consider
it as stable and performant enough for integration with Cassandra. 
> Proposed replacement can work in both on/off Heap modes (depending if JNA is available)
and doesn't blindly reallocate things, which allows to resolve CASSANDRA-4265 as "Won't Fix".

--
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