[
https://issues.apache.org/jira/browse/CASSANDRA-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934406#comment-13934406
]
Russ Hatch commented on CASSANDRA-6553:
---------------------------------------
These tests were done with a 4 node cluster using RF=3. We picked 3 scenarios
(low, high, and uber contention) and I ran each with CL=one and CL=quorum, with
counterwrite and counterread.
New counters appeared to outperform 2.0 in every aspect measured, except in the
case of competing counter reads in the same partition (aka 'uber contention').
All tests were done with 50 threads.
For "low contention" I tested incrementing/reading 10k counters all in
separate partitions (50 threads)
For "high contention" I tested incrementing/reading a single counter cell (50
threads)
For "uber contention" I tested incrementing/reading 100 counter cells within
the same partition (50 threads). I first tried this scenario with 10k cells in
the same partition but performance was degraded so badly I don't think the data
would be useful, so I bumped the cells clear down to 100.
Interactive Graphs:
CL=one:
http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.counter_low_cl_one.json&metric=op_rate&operation=counterwrite&smoothing=1
http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.counter_high_cl_one.json&metric=op_rate&operation=counterwrite&smoothing=1
http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.counter_uber_cl_one.json&metric=op_rate&operation=counterwrite&smoothing=1
CL=quorum:
http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.counter_low_cl_quorum.json&metric=op_rate&operation=counterwrite&smoothing=1
http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.counter_high_cl_quorum.json&metric=op_rate&operation=counterwrite&smoothing=1
http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.counter_uber_cl_quorum.json&metric=op_rate&operation=counterwrite&smoothing=1
> Benchmark counter improvements (counters++)
> -------------------------------------------
>
> Key: CASSANDRA-6553
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6553
> Project: Cassandra
> Issue Type: Test
> Reporter: Ryan McGuire
> Assignee: Russ Hatch
> Fix For: 2.1 beta2
>
> Attachments: high_cl_one.png, high_cl_quorum.png, low_cl_one.png,
> low_cl_quorum.png, uber_cl_one.png, uber_cl_quorum.png
>
>
> Benchmark the difference in performance between CASSANDRA-6504 and trunk.
> * Updating totally unrelated counters (different partitions)
> * Updating the same counters a lot (same cells in the same partition)
> * Different cells in the same few partitions (hot counter partition)
> benchmark:
> https://github.com/apache/cassandra/tree/1218bcacba7edefaf56cf8440d0aea5794c89a1e
> (old counters)
> compared to:
> https://github.com/apache/cassandra/tree/714c423360c36da2a2b365efaf9c5c4f623ed133
> (new counters)
> So far, the above changes should only affect the write path.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
