Whenever I look at solr users' stacktraces for disjunctions, I always notice they get BooleanScorer2.
Is there some reason for this or is it not intentional (e.g. maybe a in-order collector is always being used when its possible at least in simple cases to allow for out-of-order hits?) When I examine test contributions from clover reports (e.g. https://builds.apache.org/job/Lucene-Solr-Clover-4.x/49/clover-report/), I notice that only lucene tests, and solr spellchecking tests actually hit BooleanScorer's collect. All other solr tests hit BooleanScorer2. If its possible to allow for an out of order collector in some common cases (e.g. large disjunctions w/ minShouldMatch generated by solr queryparsers), it could be a nice performance improvement. On Mon, Nov 12, 2012 at 3:48 PM, jchen2000 <jchen...@yahoo.com> wrote: > The following was generated from jvisualvm. Seems like the perf is related to > scoring a lot. Any idea/pointer on how to customize that part? > > <http://lucene.472066.n3.nabble.com/file/n4019850/profilingResult.png> > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/customize-solr-search-scoring-for-performance-tp4019444p4019850.html > Sent from the Solr - User mailing list archive at Nabble.com.
