You might want to read my blog post about Java tuning if you haven’t already – if nothing else, it includes some ideas on studying Java garbage collection behavior,
which can sometimes offer clues:
Also, some other ideas:
Sometimes you can give Java too much memory. If you end up starving the OS so that it can’t manage other resources well, having a lot of memory available
to Java is actually a bad thing.
If you turn on debug mode in config.ini, you can see all of the Solr queries as they execute. If you copy and paste one of the Solr request URLs
into a new browser window, change localhost to the appropriate server name, and add “&debugQuery=true” to the end, you’ll see details on what Solr is actually doing. This might offer clues about where bottlenecks lie.
From: kevin smith [mailto:email@example.com]
Sent: Thursday, October 04, 2012 3:03 PM
Subject: [VuFind-General] Solr seems slow
We have switched all search links on our webpage from HIP to VuFind. We are getting much more traffic, and I have noticed some real performance drops. The first problem was my Apache settings, but I am no longer getting the Server seems
to be busy Apache errors.
I have increased the memory allocated to Java.
JAVA_OPTIONS="-server -d64 -Xms8192m -Xmx8192m -XX:+UseParallelGC -XX:NewRatio=5"
It still seems like Solr is running somewhat slowly... Any ideas about speeding things up?
Our catalog is at catalog.wakegov.com
Digital Library Manager
Wake County Public Libraries