lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doron Cohen (JIRA)" <>
Subject [jira] Commented: (LUCENE-675) Lucene benchmark: objective performance test for Lucene
Date Thu, 11 Jan 2007 07:49:27 GMT


Doron Cohen commented on LUCENE-675:

Oops... I had the impression that compiling with compliance level 1.4 is sufficient to prevent
this, but guess I need to read again what that compliance level setting guarantees exactly.

Anyhow there are a 3 things that require 1.5:
 - Boolean.parseBoolean() --> Boolean.valueOf().booleanValue()
 - String.contains() --> indexOf()
 - Class.getSimpleName() --> ?

Modifying Class.getSimpleName() to Class.getName() would not be very nice - queries prints
and task names prints would be quite ugly. To fix that I added a method simpleName(Class)
to byTask.util.Format. I am attaching an updated patch - byTask.jre1.4.patch.txt - that includes
this method and removes the Java 1.5  dependency.

Thanks for catching this!

> Lucene benchmark: objective performance test for Lucene
> -------------------------------------------------------
>                 Key: LUCENE-675
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Andrzej Bialecki 
>         Assigned To: Grant Ingersoll
>            Priority: Minor
>         Attachments: benchmark.byTask.patch, benchmark.patch,,
byTask.2.patch.txt, byTask.jre1.4.patch.txt, extract_reuters.plx,,,,, tiny.alg,
> We need an objective way to measure the performance of Lucene, both indexing and querying,
on a known corpus. This issue is intended to collect comments and patches implementing a suite
of such benchmarking tests.
> Regarding the corpus: one of the widely used and freely available corpora is the original
Reuters collection, available from
or I
propose to use this corpus as a base for benchmarks. The benchmarking suite could automatically
retrieve it from known locations, and cache it locally.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message