Re: Memory question

This is a progress update on the issue: I have tried several things and they all gave improvements. In order of magnitude they are 1) Reduced heap space from 6GB to 3GB. This on it's own has so far been the biggest win as swapping almost completely stopped after this step. 2) Began limiting t

Re: Memory question

Thanks everyone. Looks like I have lots of reading to do :-) -Original Message- From: Nader, John P To: java-user@lucene.apache.org Sent: Wed, 16 May 2012 16:27 Subject: Re: Memory question Another good link is http://www.oracle.com/technetwork/java/javase/gc-tuning-6-140523

Re: Memory question

Lutz > >-Original Message- >From: Chris Bamford [mailto:chris.bamf...@talktalk.net] >Sent: Dienstag, 15. Mai 2012 16:38 >To: java-user@lucene.apache.org >Subject: Re: Memory question > > > Hi John, > >Very interesting, thanks for the detailed explanation. It certainl

Re: Memory question

java-user@lucene.apache.org Sent: Tue, 15 May 2012 18:10 Subject: RE: Memory question It mmaps the files into virtual memory if it runs on a 64 bit JVM. Because of that you see the mmapped CFS files. This is outside Java Heap and is all *virtual* no RAM is explicitely occupied except the O/S

Re: Memory question

rs and then closes them based on how full >>the heap is getting. My worry is that if the bulk of the memory is being >>allocated outside the Jvm, how can I make sensible decisions? >> >>Thanks for any pointers / info. >> >>Chris >> >> >> >>---

RE: Memory question

Regards Lutz -Original Message- From: Chris Bamford [mailto:chris.bamf...@talktalk.net] Sent: Dienstag, 15. Mai 2012 16:38 To: java-user@lucene.apache.org Subject: Re: Memory question Hi John, Very interesting, thanks for the detailed explanation. It certainly sounds like the same

Re: Memory question

ar effect ? Thanks again, - Chris -Original Message- From: Nader, John P To: java-user@lucene.apache.org Sent: Tue, 15 May 2012 21:12 Subject: Re: Memory question We've encountered this issue and came up with a fairly good approach to address it. We are on Lucene 3.0.2 with Java 1.6.0

Re: Memory question

nd then closes them based on how full >the heap is getting. My worry is that if the bulk of the memory is being >allocated outside the Jvm, how can I make sensible decisions? > >Thanks for any pointers / info. > >Chris > > > >-Original Message- >From: u...@

Re: RE: Memory question

om: u...@thetaphi.de To: java-user@lucene.apache.org Sent: Tue, 15 May 2012 18:10 Subject: RE: Memory question It mmaps the files into virtual memory if it runs on a 64 bit JVM. Because of that you see the mmapped CFS files. This is outside Java Heap and is all *virtual* no RAM is explicitely occupied excep

RE: Memory question

It mmaps the files into virtual memory if it runs on a 64 bit JVM. Because of that you see the mmapped CFS files. This is outside Java Heap and is all *virtual* no RAM is explicitely occupied except the O/S cache. - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMai

Re: Memory question

In versions from 3.3 onwards MMapDirectory is the default on 64-bit linux. Not sure exactly what that means wrt your questions, but may well be relevant. -- Ian. On Tue, May 15, 2012 at 3:51 PM, Lutz Fechner wrote: > Hi, > > > By design memory outside the JVM heap space should not be accessib

RE: Memory question

Hi, By design memory outside the JVM heap space should not be accessible for java applications. Why you might see is the disc cache of the Linux storage subsystem. Best Regards Lutz -Original Message- From: Chris Bamford [mailto:chris.bamf...@talktalk.net] Sent: Dienstag, 15. Mai 20