On Dec 19, 2007 9:23 AM, Brian Whitman <[EMAIL PROTECTED]> wrote: > 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)?
It's pretty easy to parse access logs or solr query logs and find the offenders (I don't have any parsing code at my fingertips though...) Do these periods of slowness tend to happen right after a commit? Do the slow queries have anything in common? -Yonik
