You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Pavel Yaskevich (JIRA)" <ji...@apache.org> on 2013/05/19 22:31:16 UTC
[jira] [Commented] (CASSANDRA-5582) Replace CustomHsHaServer with
better oprtimized solution based on LMAX Disruptor.
[ https://issues.apache.org/jira/browse/CASSANDRA-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661642#comment-13661642 ]
Pavel Yaskevich commented on CASSANDRA-5582:
--------------------------------------------
[~iamaleksey] and [~vijay2win@yahoo.com] can you guys please attach benchmark numbers on your hardware to compare?
> Replace CustomHsHaServer with better oprtimized solution based on LMAX Disruptor.
> ---------------------------------------------------------------------------------
>
> Key: CASSANDRA-5582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5582
> Project: Cassandra
> Issue Type: Improvement
> Components: 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
>
>
> 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