[ https://issues.apache.org/jira/browse/CASSANDRA-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13951096#comment-13951096 ]
Aleksey Yeschenko commented on CASSANDRA-6553: ---------------------------------------------- [~rhatch] I want to revisit the stress params, later, but for now, could we compare these 3 branches against each other? 1. Stock 2.0 (https://github.com/apache/cassandra/tree/cassandra-2.0) 2. Stock 2.1 + Benedict's patch (https://github.com/iamaleksey/cassandra/tree/6553) 3. 2.1 with CASSANDRA-6880 and Benedict's patch (https://github.com/iamaleksey/cassandra/tree/6880) Two runs - one w/out the counter cache, and another one with counter cache on. In the meantime I'll think about the new stress params I'd like to run the benchmarks with. Thanks! > 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: 6553.txt, 6553.uber.quorum.bdplab.read.png, > 6553.uber.quorum.bdplab.write.png, high_cl_one.png, high_cl_quorum.png, > low_cl_one.png, low_cl_quorum.png, tracing.txt, 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)