[
https://issues.apache.org/jira/browse/CASSANDRA-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13929817#comment-13929817
]
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 everything.
> 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
>
>
> 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)
