Yes, I think you should have a play. But on an index that is as
realistic as you can make it - there may be variations in performance
of the different queries and filters depending on term frequencies and
loads of other stuff I don't understand. General point being simply
that YMMV.
--
Ian.
On
Filters are created programmatically per request (and customized for the
request) thus in order to benefit from CachingWrapperFilter we require a
mechanism for looking up CachingWrapperFilters based on the request. But this is
certainly an area worth trying (we could probably reuse each filter 10 t
Are you going to be caching and reusing the filters e.g. by
CachingWrapperFilter? The main benefit of filters is in reuse. It
takes time to build them in the first place, likely roughly equivalent
to running the underlying query although with variations as you
describe. Or are you saying that qu
Are there any best practices for constructing Filters to search efficiently?
From my non-exhaustive experiments I cannot intuit how to construct my filters
to achieve best performance.
I have an index (Lucene 4.3) of about 1.8M documents which contain a field
acting as a flag (evidence:true). Init
