[ https://issues.apache.org/jira/browse/CASSANDRA-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662196#comment-13662196 ]
Pavel Yaskevich commented on CASSANDRA-5582: -------------------------------------------- TTreadedSelectorServer could be better in dispatching new connections comparing to standard HsHa but not handling r/w as it has a lot of synchronization which TDistruptor one doesn't, that's why it shows better latency/throughput results. I believe Vijay was testing on actual 4 node cluster, I have been testing on my laptop. Aleksey also did some testing on his old laptop in disk bound scenario. > 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, 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