On Sat, Mar 5, 2011 at 7:37 PM, aaron morton aa...@thelastpickle.comwrote:
There is some additional memory usage in the JVM beyond that Heap size, in
the permanent generation. 900mb sounds like too much for that, but you can
check by connecting with JConsole and looking at the memory tab. You
I edited Peter Schuller's reply last time this came up into a FAQ:
http://wiki.apache.org/cassandra/FAQ#mmap
On Wed, Mar 9, 2011 at 11:10 AM, Casey Deccio ca...@deccio.net wrote:
On Sat, Mar 5, 2011 at 7:37 PM, aaron morton aa...@thelastpickle.com
wrote:
There is some additional memory usage
Casey,
It sounds like the JVM is behaving. Perhaps turn off mmapped
disk_access to double check that the number you are seeing as resident does not
include the mapped memory?
Aaron
On 10/03/2011, at 6:36 AM, Jonathan Ellis wrote:
I edited Peter Schuller's reply last time this came
On 03/04/2011 03:51 PM, Casey Deccio wrote:
Are you saying: that you want a smaller heap and what settings to change
to accommodate that, or that you have already set a small heap of x and
Cassandra is using significantly more than that?
Based on my observation above, the latter.
Casey
I have a small ring of cassandra nodes that have somewhat limited memory
capacity for the moment. Cassandra is eating up all the memory on these
nodes. I'm not sure where to look first in terms of reducing the foot
print. Keys cached? Compaction?
Any hints would be greatly appreciated.
On 03/04/2011 01:53 PM, Casey Deccio wrote:
I have a small ring of cassandra nodes that have somewhat limited memory
capacity for the moment. Cassandra is eating up all the memory on these
nodes. I'm not sure where to look first in terms of reducing the foot
print. Keys cached? Compaction?
On Fri, Mar 4, 2011 at 11:03 AM, Chris Burroughs
chris.burrou...@gmail.comwrote:
What do you mean by eating up the memory? Resident set size, low
memory available to page cache, excessive gc of the jvm's heap?
jvm's heap is set for half of the physical memory (1982 MB out of 4G), and
jsvc is
