[
https://issues.apache.org/jira/browse/CASSANDRA-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13666602#comment-13666602
]
Pavel Yaskevich commented on CASSANDRA-5582:
--------------------------------------------
So the numbers (4 node cluster (16 physical CPU, 128GB RAM), RF=3, 2,000,000
keys (stress -C 150 -S 512 -V)), stress was run on the separate machine.
*THsHaDisruptorServer* (reads, QUORUM) average run
{noformat}
517758,51775,51775,0.9,1.5,9.1,10
1070470,55271,55271,0.8,1.5,3.4,20
1660087,58961,58961,0.8,1.4,3.4,30
1942881,28279,28279,0.8,1.3,4.1,40
2000000,5711,5711,0.8,1.3,8.1,44
Averages from the middle 80% of values:
interval_op_rate : 55335
interval_key_rate : 55335
latency median : 0.8
latency 95th percentile : 1.4
latency 99.9th percentile : 5.6
Total operation time : 00:00:44
{noformat}
*TThreadedSelectorServer* (reads, QUORUM) average run with invoker patch applied
{noformat}
544080,54408,54408,0.7,1.5,26.8,10
1070755,52667,52667,0.8,1.5,3.3,20
1656322,58556,58556,0.7,1.5,45.8,30
1799710,14338,14338,0.7,1.5,45.8,40
1956230,15652,15652,0.8,1.5,45.8,50
2000000,4377,4377,0.8,1.4,45.8,54
Averages from the middle 80% of values:
interval_op_rate : 44992
interval_key_rate : 44992
latency median : 0.7
latency 95th percentile : 1.5
latency 99.9th percentile : 30.4
Total operation time : 00:00:54
{noformat}
Also, it's important to node that TThreadedSelectorServer was throwing few
timeout exceptions (5-10) in 1 of 4 runs.
> 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-5530-invoker-fix.patch, CASSANDRA-5582.patch,
> disruptor-3.0.1.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
