On Wednesday 07 January 2009 08:57:54 John Wang wrote:
> One more thing I missed. I don't quite get your point about skip() vs
> next().
>
> With or queries, skipping does not help as much comparing to and queries.
>
When for example 2 out of 3 iterators/scorers are required, one can
skip 'last'
On Wednesday 07 January 2009 08:55:50 John Wang wrote:
> Paul:
>
>Our very simple/naive testing methodology for OrDocIdSetIterator:
>
> 5 sub iterators, each subiterators just iterate from 0 to 1,000,000.
>
> The test iterates the OrDocIdSetIterator until next() is false.
At LUCENE-365
One more thing I missed. I don't quite get your point about skip() vs
next().
With or queries, skipping does not help as much comparing to and queries.
-John
On Tue, Jan 6, 2009 at 11:55 PM, John Wang wrote:
> Paul:
>
>Our very simple/naive testing methodology for OrDocIdSetIterator:
>
Paul:
Our very simple/naive testing methodology for OrDocIdSetIterator:
5 sub iterators, each subiterators just iterate from 0 to 1,000,000.
The test iterates the OrDocIdSetIterator until next() is false.
Do you want me to run the same test against DisjunctDisi?
-John
On Tue, Jan
On Wednesday 07 January 2009 07:36:06 John Wang wrote:
> Hi guys:
>
> We have been building a suite of boolean operators DocIdSets
> (e.g. AndDocIdSet/Iterator, OrDocIdSet/Iterator,
> NotDocIdSet/Iterator). We compared our implementation on the
> OrDocIdSetIterator (based on DisjunctionMaxScor
Hi guys:
We have been building a suite of boolean operators DocIdSets (e.g.
AndDocIdSet/Iterator, OrDocIdSet/Iterator, NotDocIdSet/Iterator). We
compared our implementation on the OrDocIdSetIterator (based on
DisjunctionMaxScorer code) with some code tuning, and we see the performance
doubled
