You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2014/02/20 05:01:20 UTC
[jira] [Commented] (CASSANDRA-6553) Benchmark counter improvements
(counters++)
[ https://issues.apache.org/jira/browse/CASSANDRA-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906581#comment-13906581 ]
Aleksey Yeschenko commented on CASSANDRA-6553:
----------------------------------------------
Or, really, just 2.0 vs. 2.1, since that's what really matters.
> 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: Ryan McGuire
> Fix For: 2.1
>
>
> 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.1.5#6160)