You may want to try the RPM tool, it will show you what inside of that QueryComponent is really slow.
http://blog.sematext.com/2010/05/11/solr-performance-monitoring-announcement/ Or you can run Solr under your own profiler. Otis ---- Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch Lucene ecosystem search :: http://search-lucene.com/ ----- Original Message ---- > From: Blargy <zman...@hotmail.com> > To: solr-user@lucene.apache.org > Sent: Fri, June 18, 2010 1:22:57 AM > Subject: Re: Peformance tuning > > > first step is to do an &debugQuery=true and see where the > time is > going on the server-side. If you're doing > highlighting of a stored > field, that can be a biggie. The > timings will be in the debug output > - be sure to look at both > sections of the timings. > Looks like the majority of the time is > spend on the QueryComponent in the Process section. Any suggestions on how I > can improve this? Thanks! -- View this message in context: > href="http://lucene.472066.n3.nabble.com/Peformance-tuning-tp904540p904861.html"; > > target=_blank > >http://lucene.472066.n3.nabble.com/Peformance-tuning-tp904540p904861.html Sent > from the Solr - User mailing list archive at Nabble.com.
