On Tuesday 10 April 2007 17:41, eks dev wrote: > > If I remember well, the last time we profiled search with "high density" OR queries scoring was taking up to 30% of the time. This was a 8Mio collection of short documents fitting comfortably in RAM. So I am sure disabling scoring in some cases could bring us something. > > I am not all that familiar with scoring inner workings to stand 100% behind this statement, so please take it with some healthy reserve.
For "high density OR" I'd guess most of the work was spent maintaining the priority queue by document number. See also LUCENE-730 . > > But anyhow, with Matcher in place, we have at least a chance to prove it brings something for this scenario. For Filtering case it brings definitely a lot. > > on the other note, > Paul, would it be possible/easy to have something like. It looks easy to add it, but I may be missing something: > BooleanQuery.add(Matcher mtr, > BooleanClause.Occur occur) That's one of the things I'd like to see added. It would allow a single ConjunctionScorer to do a filtered search for a query with some required terms. Regards, Paul Elschot --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
