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.
Erik
On Jun 17, 2010, at 9:37 PM, Blargy wrote:
After indexing our item descriptions our index grew from around
3gigs to now
17.5 and I can see our search has deteriorated from sub 50ms
searches to
over 500ms now. The sick thing is I'm not even searching across that
field
at the moment but I plan to in the near future as well as include
highlighting.
What size is considered to be "too big" for one index? When should one
looking into sharding/federation etc?
What are some generic performance tuning options that could possible
help?
We are currently hosting 4 slaves. Would increasing the number of
slaves
help?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Peformance-tuning-tp904540p904540.html
Sent from the Solr - User mailing list archive at Nabble.com.
