cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6553) Benchmark counter improvements (counters++)
Date Tue, 25 Mar 2014 21:17:17 GMT


Aleksey Yeschenko commented on CASSANDRA-6553:

[~rhatch] Thanks. Counter writes at uber contention will look decent (in these graphs) with
CASSANDRA-6880, but why the slower reads - I have no idea. The read path for counters hasn't
really changed since 2.0, so  ¯\_(ツ)_/¯.

Could be CASSANDRA-6746, could be something else. As I said before, I'd like to see the same
a similar set of benchmarks on non-counter tables, to see if regular reads would show same
weird read results 'under contention'.

> Benchmark counter improvements (counters++)
> -------------------------------------------
>                 Key: CASSANDRA-6553
>                 URL:
>             Project: Cassandra
>          Issue Type: Test
>            Reporter: Ryan McGuire
>            Assignee: Russ Hatch
>             Fix For: 2.1 beta2
>         Attachments:, 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,
> 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:
(old counters)
> compared to:
(new counters)
> So far, the above changes should only affect the write path.

This message was sent by Atlassian JIRA

View raw message