something weird happening w/ BooleanScorer... indeed, my first impression was jvm bug triggered on some rare conditions... but we tried old jvm (1.5).. the latest 1.6 U14 , -client instead of -XBatch -server....no changes
We never managed to wait so long to see it finish, so I am not sure if we are talking about some dead loop, or just extremely slow the good thing is that we can reproduce it, I asked our QA to keep exact copy of this index.... if we con help somehow just let me now ----- Original Message ---- > From: Michael McCandless <luc...@mikemccandless.com> > To: java-user@lucene.apache.org > Sent: Wednesday, 15 July, 2009 13:30:22 > Subject: Re: speed of BooleanQueries on 2.9 > > On Tue, Jul 14, 2009 at 7:04 PM, eks devwrote: > > > > I do not know exactly why, but > > when I BooleanQuery.setAllowDocsOutOfOrder(true); I have the problem, but > > with > setAllowDocsOutOfOrder(false); no problems whatsoever > > That toggles between using BooleanScorer vs BooleanScorer2. > > The odd thing is it's especially queries like yours (many OR'd terms) > that BooleanScorer's peformance should shine compared to > BooleanScorer2. > > Yet you're seeing something weird happening w/ BooleanScorer. > > Mike > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
