Op Wednesday 19 November 2008 03:39:01 schreef [EMAIL PROTECTED]:
...
>
> Our design is roughly as follows: we have some pre-query filters,
> queries typically involving around 25 clauses, and some
> post-processing of hits. We collect counts and filter post query
> using a hit collector, which use
n't have the set operations we need to use
it
directly.
Has anyone else seen this? Is there anything else
we should be changing in the upgrade to 2.4?
We are seeing something very similar to this. We had an IndexReader
per
core, and performance was ok. Since upgrading to 2.4, perfor
er type, and it doesn't have the set operations we need to use it
> directly.
>
> Has anyone else seen this? Is there anything else
> we should be changing in the upgrade to 2.4?
>
We are seeing something very similar to this. We had an IndexReader per
core, and performance was
On an index of around 20 gigs I've been seeing a performance drop of
around 35% after upgrading to 2.4 (measured on ~1 requests
identical requests, executed in parallel against a threaded lucene /
apache setup, after a roughly 1 query warmup). The principal
changes I've made so far are just
