Getting a lot of those today.
Is it all from the same site we saw last week?
OFER FORT
Head of RD
437 Fifth Avenue 9th floor, New York, NY 10016
cell: ISR +972-54-5678339 US +1 212 738 9594 ext 34
skype: oferfort
tracx
social intelligence
www.tracx.comhttp://www.tracx.com/
Follow us:
[Tracx on
I don't use any garbage collection parameters.
/Tim
2010/2/8 Simon Rosenthal simon_rosent...@yahoo.com:
What Garbage Collection parameters is the JVM using ? the memory will not
always be freed immediately after an event like unloading a core or starting
a new searcher.
2010/2/8 Tim
If I unload the core and then click Perform GC in jconsole nothing
happens. The 8 GB RAM is still used.
If I load the core again and then run the query with the sort fields,
then jconsole shows that the memory usage immediately drops to 1 GB
and then rises to 8 GB again as it caches the stuff.
Tim,
The GC just automagically works right?
:)
There's been issues around thread local in Lucene. The main code for
core management is CoreContainer, which I believe is fairly easy to
digest. If there's an issue you may find it there.
Jason
2010/2/9 Tim Terlegård tim.terleg...@gmail.com:
To me it doesn't look like unloading a Solr Core frees the memory that
the core has used. Is this how it should be?
I have a big index with 50 million documents. After loading a core it
takes 300 MB RAM. After a query with a couple of sort fields Solr
takes about 8 GB RAM. Then I unload
What Garbage Collection parameters is the JVM using ? the memory will not
always be freed immediately after an event like unloading a core or starting
a new searcher.
2010/2/8 Tim Terlegård tim.terleg...@gmail.com
To me it doesn't look like unloading a Solr Core frees the memory that
the
The 'jconsole' program lets you monitor GC operation in real-time.
http://java.sun.com/developer/technicalArticles/J2SE/jconsole.html
On Mon, Feb 8, 2010 at 8:44 AM, Simon Rosenthal
simon_rosent...@yahoo.com wrote:
What Garbage Collection parameters is the JVM using ? the memory will not
