cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6553) Benchmark counter improvements (counters++)
Date Sat, 15 Mar 2014 11:13:43 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13936149#comment-13936149
] 

Aleksey Yeschenko commented on CASSANDRA-6553:
----------------------------------------------

[~slebresne] Actually, no. I meant going further. Obviously disable the cache, but also make
sure that we are reading from disk, not the memtable. Maybe go even further and test with
data not fitting the page cache, too.

> 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)

Mime
View raw message