[
https://issues.apache.org/jira/browse/CASSANDRA-7761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14156071#comment-14156071
]
Jason Brown commented on CASSANDRA-7761:
----------------------------------------
I ran this branch on my three node cluster, and unfortunately the result was
pretty bad. I ran the trunk code (the commit previous tjake's changes) - which
entails running the insert for one round, then the reads for three rounds. I
used the "incrementing thread count" version of stress, starting with 4
threads, then 8, and all the way up to 913 threads. The branch code, however,
failed to get past 181 threads on the insert stage, and the subsequent read was
rather bad (probably because not enough data was inserted). Even at the 181
thread mark, the throughput was half that of the trunk, and latencies were
greater than double.
That being said, I reviewed the code and I like where it's going, just need to
work out the performance kinks.
> Upgrade netty
> -------------
>
> Key: CASSANDRA-7761
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7761
> Project: Cassandra
> Issue Type: Improvement
> Reporter: T Jake Luciani
> Assignee: T Jake Luciani
> Priority: Minor
> Fix For: 2.1.1
>
>
> Latest netty contains the proper fix for CASSANDRA-7695 plus some of the
> performance patches [~benedict] contributed. We should upgrade to this
> following extensive burn in testing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
