Hello,
I have discovered a serious bug in the LuceneIndexer benchmarking
app. All tests have been rerun, and the new numbers reflect a 13-15%
improvement for Lucene. I apologize for having reported bad data.
Here are some of the new results, both with and without the bug so
that you can
Hello,
A few things have changed since the first benchmarker results were
reported, and a fresh data set is mandated. A serious bug in the
LuceneIndexer was fixed. Multiple runs are now triggered from within
a single process. The report now uses a truncated mean that discards
both high
On Apr 7, 2006, at 10:05 AM, Doug Cutting wrote:
> Another axis that I don't think you're yet measuring is how things
change as
> the index grows.
There are lots of axes that I haven't measured yet, but I do have to
move on
to other things sooner or later. :) Running decent scientific
