[
https://issues.apache.org/jira/browse/CASSANDRA-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986686#action_12986686
]
Javier Canillas commented on CASSANDRA-1379:
--------------------------------------------
Actually, on the patch both reads times will impact on the only read counter.
Maybe creating a separate counter for cache reads and physical reads would be
good. On the other hand, i dont remember if there is a miss counter over cache,
if there is, it would be surely impacted
> Uncached row reads may block cached reads
> -----------------------------------------
>
> Key: CASSANDRA-1379
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1379
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: David King
> Assignee: Javier Canillas
> Priority: Minor
> Fix For: 0.7.2
>
> Attachments: CASSANDRA-1379.patch
>
>
> The cap on the number of concurrent reads appears to cap the *total* number
> of concurrent reads instead of just capping the reads that are bound for
> disk. That is, given N concurrent readers if all of them are busy waiting on
> disk, even reads that can be served from the row cache will block waiting for
> them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
