Here's a good place to start with garbage collection:
http://www.lucidimagination.com/blog/2009/09/19/java-garbage-collection-boot-camp-draft/
About precision step. Optimal means different things for different indexes.
You have
to provide a lot more detail about your problem space before anyone ca
Also, does anyone know the best precisionStep to use on a trie field (float)
definition to achieve optimal performance?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Randomly-slow-response-times-for-range-queries-tp1441724p1443096.html
Sent from the Solr - User mailing list
Well I am only sending about 50 QPS at it at the time that it temporarily
slows down, and then it's able to get all the way up to 100 QPS+ with no
problems (until the next random queries). I suppose it could be the garbage
collection. Is there a good way to limit this?
--
View this message in con
Well, throw enough queries at any server and it'll slow right down, so
how many are we talking here?
But no, there're no SOLR issues like this that I know of. That said, you
could be getting cache thrashing. You could be getting garbage collection
by the JVM. You could be executing commits somehow
