[jira] [Comment Edited] (CASSANDRA-6553) Benchmark counter improvements (counters++)
[ https://issues.apache.org/jira/browse/CASSANDRA-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13926217#comment-13926217 ] Aleksey Yeschenko edited comment on CASSANDRA-6553 at 3/10/14 10:13 PM: [~rhatch] Is there any progress on this? Can you benchmark cassandra-2.0 branch vs. https://github.com/iamaleksey/cassandra/commits/6506-nocompat ? It's becoming kinda pressing :\ Thanks. was (Author: iamaleksey): [~rhatch] Is there any progress on this? Can you benchmark cassandra-2.1 branch vs. https://github.com/iamaleksey/cassandra/commits/6506-nocompat ? It's becoming kinda pressing :\ 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 > > > 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)
[jira] [Comment Edited] (CASSANDRA-6553) Benchmark counter improvements (counters++)
[ https://issues.apache.org/jira/browse/CASSANDRA-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934404#comment-13934404 ] Russ Hatch edited comment on CASSANDRA-6553 at 3/14/14 1:14 AM: !low_cl_one.png! !high_cl_one.png! !uber_cl_one.png! !low_cl_quorum.png! !high_cl_quorum.png! !uber_cl_quorum.png|thumbnail! was (Author: rhatch): !low_cl_one.png|thumbnail! !high_cl_one.png|thumbnail! !uber_cl_one.png|thumbnail! !low_cl_quorum.png|thumbnail! !high_cl_quorum.png|thumbnail! !uber_cl_quorum.png|thumbnail! > 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)
[jira] [Comment Edited] (CASSANDRA-6553) Benchmark counter improvements (counters++)
[ https://issues.apache.org/jira/browse/CASSANDRA-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934404#comment-13934404 ] Russ Hatch edited comment on CASSANDRA-6553 at 3/14/14 1:57 AM: !low_cl_one.png! !high_cl_one.png! !uber_cl_one.png! !low_cl_quorum.png! !high_cl_quorum.png! !uber_cl_quorum.png! was (Author: rhatch): !low_cl_one.png! !high_cl_one.png! !uber_cl_one.png! !low_cl_quorum.png! !high_cl_quorum.png! !uber_cl_quorum.png|thumbnail! > 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)
[jira] [Comment Edited] (CASSANDRA-6553) Benchmark counter improvements (counters++)
[ https://issues.apache.org/jira/browse/CASSANDRA-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13938749#comment-13938749 ] Russ Hatch edited comment on CASSANDRA-6553 at 3/18/14 3:34 AM: graphs comparing [~iamaleksey]'s 2.1 branch against the 2.0 branch (with counter caching disabled): http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.counter_high_cl_one_no_counter_cache_20vs21.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.counter_high_cl_quorum_no_counter_cache_20vs21.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.counter_low_cl_one_no_counter_cache_20vs21.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.counter_low_cl_quorum_no_counter_cache_20vs21.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.counter_uber_cl_one_no_counter_cache_20vs21.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.counter_uber_cl_quorum_no_counter_cache_20vs21.json was (Author: rhatch): graphs comparing [~iamaleksey]'s 2.1 branch against the 2.0 branch: http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.counter_high_cl_one_no_counter_cache_20vs21.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.counter_high_cl_quorum_no_counter_cache_20vs21.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.counter_low_cl_one_no_counter_cache_20vs21.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.counter_low_cl_quorum_no_counter_cache_20vs21.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.counter_uber_cl_one_no_counter_cache_20vs21.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.counter_uber_cl_quorum_no_counter_cache_20vs21.json > 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)
[jira] [Comment Edited] (CASSANDRA-6553) Benchmark counter improvements (counters++)
[ https://issues.apache.org/jira/browse/CASSANDRA-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13947401#comment-13947401 ] Russ Hatch edited comment on CASSANDRA-6553 at 3/26/14 12:54 AM: - For comparison, here's graphs of 2.0 vs 2.1 for regular write/read operations (*not* counterread or counterwrite). http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.read_write.low_contention_CL_one.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.read_write.high_contention_CL_one.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.read_write.uber_contention_CL_one.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.read_write.low_contention_CL_quorum.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.read_write.high_contention_CL_quorum.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.read_write.uber_contention_CL_quorum.json I forgot to mention that in the uber contention scenarios, I had to drop the operation count down to 1.4m because around 1.5m operations there's a decline in performance and the test couldn't complete and didn't seem to recover. was (Author: rhatch): For comparison, here's graphs of 2.0 vs 2.1 for regular write/read operations (*not* counterread or counterwrite). http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.read_write.low_contention_CL_one.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.read_write.high_contention_CL_one.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.read_write.uber_contention_CL_one.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.read_write.low_contention_CL_quorum.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.read_write.high_contention_CL_quorum.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.read_write.uber_contention_CL_quorum.json > 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)
[jira] [Comment Edited] (CASSANDRA-6553) Benchmark counter improvements (counters++)
[ https://issues.apache.org/jira/browse/CASSANDRA-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13960339#comment-13960339 ] Russ Hatch edited comment on CASSANDRA-6553 at 4/4/14 8:03 PM: --- [~iamaleksey] -- here you go: http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.low_contention_CL_quorum_4_4.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.high_contention_CL_quorum_4_4.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.user_contention_CL_quorum_4_4.json btw, if you want to change the top title or legend information for better presentation, you can update the json. Clicking a color in the legend will disable/enable that dataset. If you want to make changes but don't want to push them to github, you can clone the cassandra_performance repo and run it locally from the 'graph' directory with python -m SimpleHTTPServer was (Author: rhatch): [~iamaleksey] -- here you go: http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.low_contention_CL_quorum_4_4.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.high_contention_CL_quorum_4_4.json http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6553.user_contention_CL_quorum_4_4.json btw, if you want to change the top title or legend information for better presentation, you can update the json. Clicking a legend will disable/enable that dataset. If you want to make changes but don't want to push them to github, you can clone the cassandra_performance repo and run it locally from the 'graph' directory with python -m SimpleHTTPServer > 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, > logs.tar.gz, 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)
