The build file in the benchmarker has a "run" target that shows how to
run it. The important part to port is the "by task" stuff: http://lucene.apache.org/java/2_4_0/api/contrib-benchmark/org/apache/lucene/benchmark/byTask/package-summary.html
On Feb 6, 2009, at 10:11 PM, Marvin Humphrey wrote:
Greets,
Lucy needs sophisticated search-time benchmarking. The obvious
approach is to
port the Lucene contrib benchmark suite.
However, contrib benchmark has a large number of classes, the
documentation is
sparse and occasionally wrong ("Usage: java Benchmark algorithm-
file"),
there's no howto or Wiki page (just package.html) ... and one
obvious starting
point, the "Benchmarker" class, is deprecated.
What's actually important in the benchmark suite? Besides
"Benchmarker" being
deprecated, there look to be multiple "stats" and "utils"
directories. Are
there large chunks of obsolete code that can be safely ignored?
Marvin Humphrey
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
--------------------------
Grant Ingersoll
http://www.lucidimagination.com/
Search the Lucene ecosystem (Lucene/Solr/Nutch/Mahout/Tika) using Solr/
Lucene:
http://www.lucidimagination.com/search
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
