cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6553) Benchmark counter improvements (counters++)
Date Tue, 11 Mar 2014 00:58:42 GMT


Benedict commented on CASSANDRA-6553:

bq. Those four commands all run without error.

It'll be selecting the last -col definition you provide then (so in the case I pasted, it'll
be same as -coln=FIXED(3)). I'll file a ticket and post a fix tomorrow for not erroring out.

I'll also have a look and see if we can't make the number of columns variable for counters.
It does make sense to write to a random selection of the possible counters for a single partition
key, and it may have just been laziness in not alleviating a prior limitation when I updated

> Benchmark counter improvements (counters++)
> -------------------------------------------
>                 Key: CASSANDRA-6553
>                 URL:
>             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:
(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