Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAH-t0tbS7kC0v_ZZQ8Du3VQv+z1Df6GPicejFuA=XsBS2Ew-tQ@mail.gmail.com>
References: 
 <CAH-t0tbS7kC0v_ZZQ8Du3VQv+z1Df6GPicejFuA=XsBS2Ew-tQ@mail.gmail.com>
Date: Mon, 16 Apr 2012 12:19:22 -0700
Message-ID: 
 <CACHzRHaVWMQLKs0Ku=uWuMoSZw=h+tE7d5eFeoWpF2TM0w086w@mail.gmail.com>
Subject: Re: Off-heap row cache and mmapped sstables
From: Rob Coli <rcoli@palominodb.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On 4/12/12, Omid Aladini <omidaladini@gmail.com> wrote:
> Cassandra issues an mlockall [1] before mmap-ing sstables to prevent
> the kernel from paging out heap space in favor of memory-mapped
> sstables. I was wondering, what happens to the off-heap row cache
> (saved or unsaved)? Is it possible that the kernel pages out off-heap
> row cache in favor of resident mmap-ed sstable pages?

For what it's worth, I find this conjecture plausible given my
understanding of the Cassandra ticket which resulted in the use of
JNA+mlockall. I'd love to hear an opinion from someone from the
project with more in-depth knowledge. :)

=Rob

-- 
=Robert Coli
AIM&GTALK - rcoli@palominodb.com
YAHOO - rcoli.palominob
SKYPE - rcoli_palominodb