[
https://issues.apache.org/jira/browse/CASSANDRA-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13936101#comment-13936101
]
Sylvain Lebresne commented on CASSANDRA-6553:
---------------------------------------------
bq. there are some other scenarios to test - when the read before write hits
the disk, for example
That's actually largely what I meant by testing with the counter cache
disabled. The new counter implem has a (new) counter cache that saves the
read-before-write from hitting disk on a cache hit. So a simple way to check
what happen when you run out of cache would be to just disable it, which can be
done from the yaml (check the counter_cache_* new options).
> 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)
