[
https://issues.apache.org/jira/browse/LUCENE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jingkei Ly updated LUCENE-1313:
-------------------------------
Attachment: TestLuceneNRT.java
Jason,
I've attached the benchmarking test I've based my observations on. My use case
is to add 1 document to the index and to perform a search immediately
afterwards and be guaranteed that the document I previously added is available
in the search (which it is why it is done synchronously in 1 thread).
Apologies for the sysouts on which I'm basing my observations on - the main
point is that adding a few thousand docs in this fashion appears to be faster
in Lucene 3.0 when compared to the equivalent with trunk+patch. The 1/3rd
slower observation I made is based on the fact that on my machine (quad-core,
4GB RAM, Windows XP), Lucene 3.0 is able to process 35 docs per second in the
fashion I've described, whereas trunk + patch runs at 22 docs per second.
Having rerun the test, It appears the average time it takes for a query to
complete is slower but it's actually the average time it takes to get a new
realtime reader that is much slower.
I haven't ruled out having done something really stupid in my test, in which
case I apologise in advance!
> Near Realtime Search (using a built in RAMDirectory)
> ----------------------------------------------------
>
> Key: LUCENE-1313
> URL: https://issues.apache.org/jira/browse/LUCENE-1313
> Project: Lucene - Java
> Issue Type: New Feature
> Components: Index
> Affects Versions: 2.4.1
> Reporter: Jason Rutherglen
> Priority: Minor
> Fix For: 3.1
>
> Attachments: LUCENE-1313.jar, LUCENE-1313.patch, LUCENE-1313.patch,
> LUCENE-1313.patch, LUCENE-1313.patch, LUCENE-1313.patch, LUCENE-1313.patch,
> LUCENE-1313.patch, LUCENE-1313.patch, LUCENE-1313.patch, LUCENE-1313.patch,
> LUCENE-1313.patch, LUCENE-1313.patch, LUCENE-1313.patch, LUCENE-1313.patch,
> LUCENE-1313.patch, LUCENE-1313.patch, LUCENE-1313.patch, LUCENE-1313.patch,
> LUCENE-1313.patch, LUCENE-1313.patch, LUCENE-1313.patch, LUCENE-1313.patch,
> LUCENE-1313.patch, LUCENE-1313.patch, LUCENE-1313.patch, LUCENE-1313.patch,
> LUCENE-1313.patch, LUCENE-1313.patch, LUCENE-1313.patch, lucene-1313.patch,
> lucene-1313.patch, lucene-1313.patch, lucene-1313.patch, TestLuceneNRT.java
>
>
> Enable near realtime search in Lucene without external
> dependencies. When RAM NRT is enabled, the implementation adds a
> RAMDirectory to IndexWriter. Flushes go to the ramdir unless
> there is no available space. Merges are completed in the ram
> dir until there is no more available ram.
> IW.optimize and IW.commit flush the ramdir to the primary
> directory, all other operations try to keep segments in ram
> until there is no more space.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
