From 515cf2153a46d1ebc4c95f413da05261b211bbec Mon Sep 17 00:00:00 2001 From: Daniel Naber Date: Sun, 12 Sep 2004 11:36:59 +0000 Subject: [PATCH] slightly improve the benchmark template: add Lucene version, query speed git-svn-id: https://svn.apache.org/repos/asf/lucene/java/trunk@150502 13f79535-47bb-0310-9956-ffa450edef68 --- docs/benchmarks.html | 12 ++++++++---- docs/benchmarktemplate.xml | 6 +++++- xdocs/benchmarks.xml | 12 ++++++++---- 3 files changed, 21 insertions(+), 9 deletions(-) diff --git a/docs/benchmarks.html b/docs/benchmarks.html index 9ffa5136899..80f48d3efa6 100644 --- a/docs/benchmarks.html +++ b/docs/benchmarks.html @@ -179,6 +179,7 @@ limitations under the License.

Software environment
+

  • Lucene Version: Self-explanatory
  • Java Version: Version of Java SDK/JRE that is run
  • Java VM: Server/client VM, Sun VM/JRockIt
    • @@ -197,7 +198,7 @@ limitations under the License. Self-explanatory
  • Source documents storage location: Where are the documents being indexed located? - Filesystem, DB, http,etc
    • + Filesystem, DB, http, etc.
  • File type of source documents: Types of files being indexed, e.g. HTML files, XML files, PDF files, etc.
  • Parser(s) used, if any: Parsers used for parsing the @@ -208,7 +209,7 @@ limitations under the License. Document contains
  • Type of fields: Type of each field
  • Index persistence: Where the index is stored, e.g. - FSDirectory, SqlDirectory, etc
    • + FSDirectory, SqlDirectory, etc.

    Figures
    @@ -217,11 +218,14 @@ limitations under the License.

  • Time taken / 1000 docs indexed: Time taken to index 1000 files
  • Memory consumption: Self-explanatory
    • +
  • Query speed: average time a query takes, type + of queries (e.g. simple one-term query, phrase query), + not measuring any overhead outside Lucene

    • Notes

  • Notes: Any comments which don't belong in the above, - special tuning/strategies, etc
    • + special tuning/strategies, etc.

    @@ -503,7 +507,7 @@ limitations under the License. XSL transformation on them, and then proceeded to index the stream. The indexer optimized the index every 50,000 documents (on this run) though previously, we optimized every 300,000 documents. The performance didn't change much either way. We did no other - tuning (RAM Directories, separate process to pretransform the source material, etc) + tuning (RAM Directories, separate process to pretransform the source material, etc.) to make it index faster. When all of these individual indexes were built, they were merged together into the main index. That process usually took ~ a day.

    diff --git a/docs/benchmarktemplate.xml b/docs/benchmarktemplate.xml index 82a1c97dbce..df7601f20f9 100644 --- a/docs/benchmarktemplate.xml +++ b/docs/benchmarktemplate.xml @@ -11,11 +11,12 @@ RAID-5)

    Software environment
    +

  • Lucene Version: Self-explanatory
  • Java Version: Version of Java SDK/JRE that is run
  • Java VM: Server/client VM, Sun VM/JRockIt
  • OS Version: Self-explanatory
  • Location of index: Is the index stored in filesystem or -database? Is it on the same server(local) or +database? Is it on the same server (local) or over the network?

    • @@ -47,6 +48,9 @@ runs): Time taken to index to index all files

  • Time taken / 1000 docs indexed: Time taken to index 1000 files
  • Memory consumption: Self-explanatory
    • +
  • Query speed: average time a query takes, type + of queries (e.g. simple one-term query, phrase query), + not measuring any overhead outside Lucene

    • Notes
    diff --git a/xdocs/benchmarks.xml b/xdocs/benchmarks.xml index 74e36ceab91..d485045f834 100644 --- a/xdocs/benchmarks.xml +++ b/xdocs/benchmarks.xml @@ -38,6 +38,7 @@

    Software environment
    +

  • Lucene Version: Self-explanatory
  • Java Version: Version of Java SDK/JRE that is run
  • Java VM: Server/client VM, Sun VM/JRockIt
    • @@ -56,7 +57,7 @@ Self-explanatory
  • Source documents storage location: Where are the documents being indexed located? - Filesystem, DB, http,etc
    • + Filesystem, DB, http, etc.
  • File type of source documents: Types of files being indexed, e.g. HTML files, XML files, PDF files, etc.
  • Parser(s) used, if any: Parsers used for parsing the @@ -67,7 +68,7 @@ Document contains
  • Type of fields: Type of each field
  • Index persistence: Where the index is stored, e.g. - FSDirectory, SqlDirectory, etc
    • + FSDirectory, SqlDirectory, etc.

    Figures
    @@ -76,11 +77,14 @@

  • Time taken / 1000 docs indexed: Time taken to index 1000 files
  • Memory consumption: Self-explanatory
    • +
  • Query speed: average time a query takes, type + of queries (e.g. simple one-term query, phrase query), + not measuring any overhead outside Lucene

    • Notes

  • Notes: Any comments which don't belong in the above, - special tuning/strategies, etc
    • + special tuning/strategies, etc.

    @@ -329,7 +333,7 @@ XSL transformation on them, and then proceeded to index the stream. The indexer optimized the index every 50,000 documents (on this run) though previously, we optimized every 300,000 documents. The performance didn't change much either way. We did no other - tuning (RAM Directories, separate process to pretransform the source material, etc) + tuning (RAM Directories, separate process to pretransform the source material, etc.) to make it index faster. When all of these individual indexes were built, they were merged together into the main index. That process usually took ~ a day.