Brian (moving to solr-user), Sounds like GC to me. That is, the JVM not having large enough heap. Run jconsole and you'll quickly see if this guess is correct or not (kill -QUIT is also your friend, believe it or not).
We recently had somebody who had a nice little Solr spellchecker instance running, but after awhile it would "stop responding". We looked at the command-line used to invoke the servlet container and didn't see -Xmx..... :) Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch ----- Original Message ---- From: Brian Whitman <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Sent: Wednesday, December 19, 2007 9:23:01 AM Subject: debugging slowness We've got periods where direct solr queries take 35s; on resin reboot they go back to taking 500ms. This is on a 16GB ram 4-core server. We want to debug this but don't know where to start. Is there some sample- type command we can run during queries to figure out where Solr/Lucene is spending its time (ala MySQL's slow query log)?
