cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2252) arena allocation for memtables
Date Thu, 25 Aug 2011 18:54:38 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091216#comment-13091216
] 

Jonathan Ellis commented on CASSANDRA-2252:
-------------------------------------------

I see what you mean: you want to allow a Region to "die" if all the buffers it was responsible
for have been overwritten and thus the Region is no longer needed for flush.  In that case,
weak references sound reasonable.  However, I'm not sure it would make any difference in practice
since we allocate row keys into the regions, as well.

> arena allocation for memtables
> ------------------------------
>
>                 Key: CASSANDRA-2252
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2252
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>             Fix For: 1.0
>
>         Attachments: 0001-add-MemtableAllocator.txt, 0002-add-off-heap-MemtableAllocator-support.txt,
2252-v3.txt, 2252-v4.txt, merged-2252.tgz
>
>
> The memtable design practically actively fights Java's GC design.  Todd Lipcon gave a
good explanation over on HBASE-3455.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message