Vectors for every hit or something, then that would
generate alot of garbage (but also run very slowly for a large index).
Mike
Magnus Rundberget wrote:
hmmm,
Well in production (1024M heap), it seems that after a while (some
hundred user queries) the memory starts reaching the max threshold
(which would boost up the footprint again :) ).
Regards,
Khawaja
On Wed, Dec 3, 2008 at 10:27 PM, Magnus Rundberget <[EMAIL PROTECTED]>
wrote:
Well...
after various tests I downgraded to lucene 1.9.1 to see if that
had any
effect... doesn't seem that way.
I have set up a JMeter te
to use up heap space)
before sweeping?
One thing to try (only for testing) might be a lower and lower -Xmx
until you do hit OOME; then you'll know the "real" memory usage of
the app.
Mike
Magnus Rundberget wrote:
Sure,
Tried with the following
Java version: build 1.
avase/technologies/hotspot/gc/gc_tuning_6.html?
2008/12/3 Magnus Rundberget <[EMAIL PROTECTED]>:
Hi,
We have an application using Tomcat, Spring etc and Lucene 2.4.0.
Our index is about 100MB (in test) and has about 20 indexed fields.
Performance is pretty good, but we are experiencing
nd you need to close that too. This might be the cause
of memory leak.
Regards
Ganesh
- Original Message - From: "Magnus Rundberget"
<[EMAIL PROTECTED]>
To:
Sent: Wednesday, December 03, 2008 4:03 PM
Subject: lucene nicking all my memory
Hi,
We have an appl
Hi,
We have an application using Tomcat, Spring etc and Lucene 2.4.0.
Our index is about 100MB (in test) and has about 20 indexed fields.
Performance is pretty good, but we are experiencing a very high usage
of memory when searching.
Looking at JConsole during a somewhat silly scenario (but
Hi,
We have an application using Tomcat, Spring etc and Lucene 2.4.0.
Our index is about 100MB (in test) and has about 20 indexed fields.
Performance is pretty good, but we are experiencing a very high usage
of memory when searching.
Looking at JConsole during a somewhat silly scenario (but
