Thanks for the quick answer ! I've just downloaded the 1.2 release jar, and my test gives me the same results. The more threads I've got, the slower Datefiltering gets (performance degradation is almost exponential). I tried to use the RangeQuery, as advised by Scott Ganyo, but it does not work very well. RangeQuery creates a TermQuery for each term within lowerTerm and higherTerm. If my range is too high, as I've got thoushands of documents, it just blows up memory... Is there any way to avoid sharing the TermInfosReader between all threads when creating the Bitset, or somehow avoid synchronizing the get method (if it is actually the bottleneck here) ?
Thanks, Sylvain --- Doug Cutting <[EMAIL PROTECTED]> a �crit�: > What version of Lucene are you using? There was a > patch made in January > to address multi-threaded performance of DateFilter. > > Doug > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran�ais ! Yahoo! Mail : http://fr.mail.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
