svn commit: r478082 - /lucene/java/trunk/contrib/memory/src/java/org/apache/lucene/index/memory/MemoryIndex.java

[wh...@apache.org]

Author: whoschek
Date: Wed Nov 22 00:20:55 2006
New Revision: 478082

URL: http://svn.apache.org/viewvc?view=rev&rev=478082
Log:
cosmetics

Modified:
    lucene/java/trunk/contrib/memory/src/java/org/apache/lucene/index/memory/MemoryIndex.java

Modified: lucene/java/trunk/contrib/memory/src/java/org/apache/lucene/index/memory/MemoryIndex.java
URL: http://svn.apache.org/viewvc/lucene/java/trunk/contrib/memory/src/java/org/apache/lucene/index/memory/MemoryIndex.java?view=diff&rev=478082&r1=478081&r2=478082
==============================================================================
--- lucene/java/trunk/contrib/memory/src/java/org/apache/lucene/index/memory/MemoryIndex.java (original)
+++ lucene/java/trunk/contrib/memory/src/java/org/apache/lucene/index/memory/MemoryIndex.java Wed Nov 22 00:20:55 2006
@@ -154,6 +154,10 @@
  * Indexing a field with N tokens takes O(N) in the best case, and O(N logN) in the worst 
  * case. Memory consumption is probably larger than for <code>RAMDirectory</code>.
  * <p>
+ * Example throughput of many simple term queries over a single MemoryIndex: 
+ * ~500000 queries/sec on a MacBook Pro, jdk 1.5.0_06, server VM. 
+ * As always, your mileage may vary.
+ * <p>
  * If you're curious about
  * the whereabouts of bottlenecks, run java 1.5 with the non-perturbing '-server
  * -agentlib:hprof=cpu=samples,depth=10' flags, then study the trace log and