[
https://issues.apache.org/jira/browse/LUCENE-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12693414#action_12693414
]
Michael McCandless commented on LUCENE-1577:
--------------------------------------------
Are these tests measuring adding a single doc, then searching on it? What are
the numbers you measure in the results (eg 25882 for LuceneRealtimeWriter)?
I think we need a more realistic test for near real-time search, but I'm not
sure exactly what that is.
In LUCENE-1516 I've added a benchmark task to periodically open a new near
real-time reader from the writer, and then tested it while doing bulk indexing.
But that's not a typical test, I think (normally bulk indexing is done up
front, and only a "trickle" of updates to doc are then done for near real-time
search). Maybe we just need an updateDocument task, which randomly picks a doc
(identified by a primary-key "docid" field) and replaces it. Then, benchmark
already has the ability to rate-limit how frequently docs are updated.
> Benchmark of different in RAM realtime techniques
> -------------------------------------------------
>
> Key: LUCENE-1577
> URL: https://issues.apache.org/jira/browse/LUCENE-1577
> Project: Lucene - Java
> Issue Type: Improvement
> Components: contrib/*
> Affects Versions: 2.4.1
> Reporter: Jason Rutherglen
> Priority: Minor
> Fix For: 2.9
>
> Attachments: LUCENE-1577.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> A place to post code that benchmarks the differences in the speed of indexing
> and searching using different realtime techniques.
--
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
