[
https://issues.apache.org/jira/browse/CASSANDRA-820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836770#action_12836770
]
Brandon Williams edited comment on CASSANDRA-820 at 2/22/10 6:24 PM:
---------------------------------------------------------------------
It's worth noting that during reads/inserts you would expect the op rate to be
equal to the key rate, but this isn't always the case due the concurrent
processes involved, however they should always be fairly close. Key rate has
no real meaning during these operations anyway, it is only included so that
that the output format is consistent between all the operations.
was (Author: brandon.williams):
It's worth noting that during reads/inserts where you would expect the op
rate to be equal to the key rate, but this isn't always the case due the
concurrent processes involved, however they should always be fairly close. Key
rate has no real meaning during these operations anyway, it is only included so
that that the output format is consistent between all the operations.
> add key counts to stress.py
> ---------------------------
>
> Key: CASSANDRA-820
> URL: https://issues.apache.org/jira/browse/CASSANDRA-820
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Priority: Minor
> Attachments: 820.patch
>
>
> stress.py currently counts interval op rates, but in the case of range
> slices, interval key rates should also be tracked.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
