[LUCENE-2061] Create benchmark & approach for testing Lucene's near real-time performance

• Type: Task
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: core/index
• Lucene Fields: New
• Assignee: Michael McCandless
• Reporter: Michael McCandless
• Created: 13/Nov/09 15:07
• Updated: 28/Aug/22 12:14

Description

With the improvements to contrib/benchmark in LUCENE-2050, it's now
possible to create compelling algs to test indexing & searching
throughput against a periodically reopened near-real-time reader from
the IndexWriter.

Coming out of the discussions in LUCENE-1526, I think to properly
characterize NRT, we should measure net search throughput as a
function of both reopen rate (ie how often you get a new NRT reader
from the writer) and indexing rate. We should also separately measure
pure adds vs updates (deletes + adds); the latter is much more work
for Lucene.

This can help apps make capacity decisions... and can help us test
performance of pending improvements for NRT (eg LUCENE-1313,
LUCENE-2047).