first u should know ur goal.
second u should analyzer ur search interface which fit for ur customer
third u analyzer ur queries(optimize solr with more used queries)
40 Threads /s does it mean u use 40 solr instances or it just show higher
user queries?
2007/5/21, Yonik Seeley <[EMAIL PROTECT
What are some typical examples of your queries (all of the params that
are sent to Solr)?
Query and Document caches typically result in small increases in performance.
The filterCache can result in large increases, depending on the queries.
Another possibility is that you may be hitting some othe
Thanks to both of you for your responses - Otis and Chris. We did manage
to run some benchmarks, but we think there are some surprising results
here. It seems that caching is not affecting performance that much. Is
that because of the small index size?
Do these seem ok or is there any room for
Hi Ajanta,
I think you answered your own questions. Either use Filters or partition the
index. The advantage of partitioning is that you can update them separately
without affecting filters, cache, searcher, etc. for the other indices (i.e. no
need to warm up with data from the other indices)
: show specific results based on a specific field - territory field and
: depending on where in the world you're coming from we'd like to show you
: advantage? Is there a way we can hint solr/lucene to use this information to
: provide better results? We could use filters on territory or we could
