You mentioned earlier that you are not setting -Xms/-Xmx; the values actually in use would then depend on the Java version, whether you're running 32- or 64-bit Java, whether Java thinks your machines are "servers", and whether you have specified the "-server" flag – and possibly a few other things.
What do you get if you run the command below? java -XX:+PrintFlagsFinal -version (Ref: http://stackoverflow.com/questions/3428251/is-there-a-default-xmx-setting-for-java-1-5 for details; I "stole" the incantation above from that location, but there are more complete examples of how it could be used there.) Note: you need to adjust the command line so that it uses the same java version as the one you're using, and also add whatever JRE-modifying parameters that you use when starting Solr. On 22 Nov 2013, at 18:12 , Dave Seltzer <dselt...@tveyes.com> wrote: > Thanks so much Shawn, > > I think you (and others) are completely right about this being heap and GC > related. I just did a test while not indexing data and the same periodic > slowness was observable. > > On to GC/Memory Tuning!
