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

Russ Hatch commented on CASSANDRA-6553:
---------------------------------------

Those four commands all run without error. If I try the uniform syntax 
suggested above an exception bubbles up:
{noformat}
java.lang.IllegalStateException: Variable column counts not supported for 
counters
        at 
org.apache.cassandra.stress.operations.ThriftCounterAdder.<init>(ThriftCounterAdder.java:37)
        at 
org.apache.cassandra.stress.StressAction.createOperation(StressAction.java:493)
        at 
org.apache.cassandra.stress.StressAction.createOperation(StressAction.java:446)
        at 
org.apache.cassandra.stress.StressAction.access$300(StressAction.java:38)
        at 
org.apache.cassandra.stress.StressAction$Consumer.run(StressAction.java:292)
{noformat}
I think that's how I settled on the funky syntax you noticed above. I tried 
many different combinations but couldn't seem to get the partition/cell counts 
I wanted any other way.

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

Reply via email to