[
https://issues.apache.org/jira/browse/CASSANDRA-6838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-6838:
--------------------------------------
Reviewer: Jonathan Ellis
Priority: Minor (was: Major)
Fix Version/s: 2.0.7
> FileCacheService overcounting its memoryUsage
> ---------------------------------------------
>
> Key: CASSANDRA-6838
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6838
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Benedict
> Assignee: Benedict
> Priority: Minor
> Labels: performance
> Fix For: 2.0.7, 2.1 beta2
>
> Attachments: 6838.txt
>
>
> On investigating why I was seeing dramatically worse performance for counter
> updates over prepared CQL3 statements compred to unprepared CQL2 statements,
> I stumbled upon a bug in FileCacheService wherein, on returning a cached
> reader back to the pool, its memory is counted again towards the total memory
> usage, but is not matched by a decrement when checked out. So we effectively
> are probably not caching readers most of the time.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
