[
https://issues.apache.org/jira/browse/LUCENE-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020217#comment-13020217
]
Earwin Burrfoot commented on LUCENE-2571:
-----------------------------------------
bq. Merges are NOT blocking indexing on trunk no matter which MP you use.
Well.. merges tie up IO (especially if not on fancy SSDs/RAIDs), which in turn
lags flushes -> bigger delays for stop the world flushes / lower bandwith cap
(after which they are forced to stop the world) for parallel flushes.
So Lance's point is partially valid.
> Indexing performance tests with realtime branch
> -----------------------------------------------
>
> Key: LUCENE-2571
> URL: https://issues.apache.org/jira/browse/LUCENE-2571
> Project: Lucene - Java
> Issue Type: Task
> Components: Index
> Reporter: Michael Busch
> Priority: Minor
> Fix For: Realtime Branch
>
> Attachments: wikimedium.realtime.Standard.nd10M_dps.png,
> wikimedium.realtime.Standard.nd10M_dps_addDocuments.png,
> wikimedium.realtime.Standard.nd10M_dps_addDocuments_flush.png,
> wikimedium.trunk.Standard.nd10M_dps.png,
> wikimedium.trunk.Standard.nd10M_dps_addDocuments.png
>
>
> We should run indexing performance tests with the DWPT changes and compare to
> trunk.
> We need to test both single-threaded and multi-threaded performance.
> NOTE: flush by RAM isn't implemented just yet, so either we wait with the
> tests or flush by doc count.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
