Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 11 Apr 2011 19:20:05 +0000 (UTC)
From: "Stu Hood (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <1434215170.50172.1302549605773.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1615101526.1752.1298704401777.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CASSANDRA-2252) off-heap memtables
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stu Hood updated CASSANDRA-2252:
--------------------------------

    Attachment: merged-2252.tgz

Rebased for trunk. I took the easy way out and just included the Allocator's allocation count in the memtable live size: this will overcount, but it accounts for fragmentation due to updates. I've started a patch for JAMM to add a mode that will allow us to ignore shared buffers: see [jamm/buffer-behavior|https://github.com/stuhood/jamm/commits/buffer-behavior].

> off-heap 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, merged-2252.tgz
>
>   Original Estimate: 0.4h
>  Remaining Estimate: 0.4h
>
> 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