[
https://issues.apache.org/jira/browse/CASSANDRA-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100604#comment-13100604
]
Stu Hood edited comment on CASSANDRA-3162 at 9/8/11 7:19 PM:
-------------------------------------------------------------
That's true, but I didn't think that was the goal of this ticket.
EDIT: I'm fine either way, so +1 if you prefer the WeakReference approach.
was (Author: stuhood):
That's true, but I didn't think that was the goal of this ticket.
> 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
