[
https://issues.apache.org/jira/browse/CASSANDRA-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100669#comment-13100669
]
Hudson commented on CASSANDRA-3162:
-----------------------------------
Integrated in Cassandra #1092 (See
[https://builds.apache.org/job/Cassandra/1092/])
use weak references to track slab regions
patch by jbellis; reviewed by stuhood for CASSANDRA-3162
jbellis :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1166876
Files :
* /cassandra/trunk/src/java/org/apache/cassandra/utils/SlabAllocator.java
> use weak references to SlabAllocator regions
> --------------------------------------------
>
> Key: CASSANDRA-3162
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3162
> Project: Cassandra
> Issue Type: Improvement
> Affects Versions: 1.0
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 1.0
>
> Attachments: 3162.txt
>
>
> Yang points out on CASSANDRA-2252,
> "Conceivably, one region would contain bytebuffer values of similar age. as
> more updates come in, all the columns in older regions are likely to have all
> died out, thus allowing us to free the entire region before flushing happens."
> So it's a bit of a corner case optimization, but easy to do and safe.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
