On Wed, 2014-02-05 at 08:17 +0100, Sathya wrote: > I am running single instance solr and the JVM heap space is minimum 6.3gb > and maximum 24.31gb. Nothing is running to complete the 24gb except tomcat > server. I have only 2 copyField entries only.
Your Xmx is the same size as your RAM. It should never be that high. When your Solr server is hammered, it will gradually expand the heap. Once expanded, it never contracts. Each time the heap expands, you get less RAM for disk caching and more GC overhead. Solr benefits little from extra memory: You are normally better off by leaving a large amount of memory for disk cache. Ideally, experiment with Xmx until you find the minimum amount required to run, then increase it by 50% or so (for unexpected scenarios). At the very least, set Xmx to 16GB, so that the system is guaranteed to have memory enough to cache most of the index. Guessing wildly: Even 6.3GB sounds high for such a small corpus. Have you tried with just 2GB? - Toke Eskildsen, State and University Library, Denmark
