dnaber 2004/09/12 04:36:59
Modified: docs benchmarktemplate.xml benchmarks.html
xdocs benchmarks.xml
Log:
slightly improve the benchmark template: add Lucene version, query speed
Revision Changes Path
1.2 +5 -1 jakarta-lucene/docs/benchmarktemplate.xml
Index: benchmarktemplate.xml
===================================================================
RCS file: /home/cvs/jakarta-lucene/docs/benchmarktemplate.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- benchmarktemplate.xml 4 Dec 2002 05:46:43 -0000 1.1
+++ benchmarktemplate.xml 12 Sep 2004 11:36:58 -0000 1.2
@@ -11,11 +11,12 @@
</p>
<p>
<b>Software environment</b><br/>
+ <li><i>Lucene Version</i>: Self-explanatory</li>
<li><i>Java Version</i>: Version of Java SDK/JRE that is run </li>
<li><i>Java VM</i>: Server/client VM, Sun VM/JRockIt</li>
<li><i>OS Version</i>: Self-explanatory</li>
<li><i>Location of index</i>: 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?</li>
</p>
<p>
@@ -47,6 +48,9 @@
<li><i>Time taken / 1000 docs indexed</i>: Time taken to index 1000
files</li>
<li><i>Memory consumption</i>: Self-explanatory</li>
+ <li><i>Query speed</i>: average time a query takes, type
+ of queries (e.g. simple one-term query, phrase query),
+ not measuring any overhead outside Lucene</li>
</p>
<p>
<b>Notes</b><br/>
1.17 +8 -4 jakarta-lucene/docs/benchmarks.html
Index: benchmarks.html
===================================================================
RCS file: /home/cvs/jakarta-lucene/docs/benchmarks.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- benchmarks.html 18 May 2004 13:32:00 -0000 1.16
+++ benchmarks.html 12 Sep 2004 11:36:58 -0000 1.17
@@ -179,6 +179,7 @@
</p>
<p>
<b>Software environment</b><br />
+ <li><i>Lucene Version</i>: Self-explanatory</li>
<li><i>Java Version</i>: Version of Java SDK/JRE that is run
</li>
<li><i>Java VM</i>: Server/client VM, Sun VM/JRockIt</li>
@@ -197,7 +198,7 @@
Self-explanatory</li>
<li><i>Source documents storage location</i>: Where are the
documents being indexed located?
- Filesystem, DB, http,etc</li>
+ Filesystem, DB, http, etc.</li>
<li><i>File type of source documents</i>: Types of files
being
indexed, e.g. HTML files, XML files, PDF files,
etc.</li>
<li><i>Parser(s) used, if any</i>: Parsers used for parsing
the
@@ -208,7 +209,7 @@
Document contains</li>
<li><i>Type of fields</i>: Type of each field</li>
<li><i>Index persistence</i>: Where the index is stored,
e.g.
- FSDirectory, SqlDirectory, etc</li>
+ FSDirectory, SqlDirectory, etc.</li>
</p>
<p>
<b>Figures</b><br />
@@ -217,11 +218,14 @@
<li><i>Time taken / 1000 docs indexed</i>: Time taken to
index
1000 files</li>
<li><i>Memory consumption</i>: Self-explanatory</li>
+ <li><i>Query speed</i>: average time a query takes, type
+ of queries (e.g. simple one-term query, phrase query),
+ not measuring any overhead outside Lucene</li>
</p>
<p>
<b>Notes</b><br />
<li><i>Notes</i>: Any comments which don't belong in the
above,
- special tuning/strategies, etc</li>
+ special tuning/strategies, etc.</li>
</p>
</ul>
</p>
@@ -503,7 +507,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.
</p>
1.4 +8 -4 jakarta-lucene/xdocs/benchmarks.xml
Index: benchmarks.xml
===================================================================
RCS file: /home/cvs/jakarta-lucene/xdocs/benchmarks.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- benchmarks.xml 26 Jan 2004 18:23:55 -0000 1.3
+++ benchmarks.xml 12 Sep 2004 11:36:59 -0000 1.4
@@ -38,6 +38,7 @@
</p>
<p>
<b>Software environment</b><br/>
+ <li><i>Lucene Version</i>: Self-explanatory</li>
<li><i>Java Version</i>: Version of Java SDK/JRE that is run
</li>
<li><i>Java VM</i>: Server/client VM, Sun VM/JRockIt</li>
@@ -56,7 +57,7 @@
Self-explanatory</li>
<li><i>Source documents storage location</i>: Where are the
documents being indexed located?
- Filesystem, DB, http,etc</li>
+ Filesystem, DB, http, etc.</li>
<li><i>File type of source documents</i>: Types of files
being
indexed, e.g. HTML files, XML files, PDF files,
etc.</li>
<li><i>Parser(s) used, if any</i>: Parsers used for parsing
the
@@ -67,7 +68,7 @@
Document contains</li>
<li><i>Type of fields</i>: Type of each field</li>
<li><i>Index persistence</i>: Where the index is stored,
e.g.
- FSDirectory, SqlDirectory, etc</li>
+ FSDirectory, SqlDirectory, etc.</li>
</p>
<p>
<b>Figures</b><br/>
@@ -76,11 +77,14 @@
<li><i>Time taken / 1000 docs indexed</i>: Time taken to
index
1000 files</li>
<li><i>Memory consumption</i>: Self-explanatory</li>
+ <li><i>Query speed</i>: average time a query takes, type
+ of queries (e.g. simple one-term query, phrase query),
+ not measuring any overhead outside Lucene</li>
</p>
<p>
<b>Notes</b><br/>
<li><i>Notes</i>: Any comments which don't belong in the
above,
- special tuning/strategies, etc</li>
+ special tuning/strategies, etc.</li>
</p>
</ul>
</p>
@@ -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.
</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
