[
https://issues.apache.org/jira/browse/CASSANDRA-9558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14575241#comment-14575241
]
Andy Tolbert commented on CASSANDRA-9558:
-----------------------------------------
Just confirming that this is very likely the java driver. I went back to
cassandra-2.1 branch and built it with driver 2.2.0-rc1-SNAPSHOT and noticed
the same performance degradation. [~tjake] is on point in that this is likely
caused by the driver only using a single connection. To get around this we
could force protocol version 2 in the driver in the stress tool, it's not ideal
but worth a try. I'll attach some performance numbers shortly.
> Cassandra-stress regression in 2.2
> ----------------------------------
>
> Key: CASSANDRA-9558
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9558
> Project: Cassandra
> Issue Type: Bug
> Reporter: Alan Boudreault
> Priority: Blocker
> Attachments: 2.1.log, 2.2.log
>
>
> We are seeing some regression in performance when using cassandra-stress 2.2.
> You can see the difference at this url:
> http://riptano.github.io/cassandra_performance/graph_v5/graph.html?stats=stress_regression.json&metric=op_rate&operation=1_write&smoothing=1&show_aggregates=true&xmin=0&xmax=108.57&ymin=0&ymax=168147.1
> The cassandra version of the cluster doesn't seem to have any impact.
> //cc [~tjake] [~benedict]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
