[ https://issues.apache.org/jira/browse/CASSANDRA-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13947138#comment-13947138 ]
Russ Hatch commented on CASSANDRA-6553: --------------------------------------- more test data, comparing 2.0 vs 2.1, with count cache disabled: The "uber contention" scenario was corrected for these tests. Earlier tests were updating all 100 contended cells in *each* operation. These tests now update one cell per operation, chosen from a uniform distribution of the 100 cells. This was the original intention of the uber contention tests, but I was using cassandra-stress incorrectly earlier. http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.low_contention_no_cache_CL_one.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.high_contention_no_cache_CL_one.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.uber_contention_no_cache_CL_one.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.low_contention_no_cache_CL_quorum.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.high_contention_no_cache_CL_quorum.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.user_contention_no_cache_CL_quorum.json uber contention counter read and writes both show some odd results. CL.ONE writes degraded until stress gave up on the test. > 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.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)