cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Doubleday <daniel.double...@gmx.net>
Subject Re: JNA to avoid swap but physical memory increase
Date Mon, 18 Jul 2011 09:47:12 GMT
http://permalink.gmane.org/gmane.comp.db.cassandra.user/14225

but given

https://issues.apache.org/jira/browse/CASSANDRA-2868

and me thinking 2 secs longer I guess it was the leaked native memory from gc inspector that
has been swapped out.

(I didn't believe that mlockall is broken but at that time no one could explain why the process
was swapping anyway)


On Jul 15, 2011, at 6:04 PM, Peter Schuller wrote:

>> Also our experience shows that the jna call does not prevent swapping so the
>> general advice is disable swap.
> 
> That sounds extremely non-likely as it would imply the kernel fails to
> honor a successful mlockall(), unless other processes on the same
> machine are being swapped out. Did the process really have permission
> to do the mlockall()?
> 
> (Not that I disagree in any way that swap should be disabled, +1 on that.)
> 
> -- 
> / Peter Schuller (@scode on twitter)


Mime
View raw message