Otis Gospodnetic created LUCENE-5134:
----------------------------------------
Summary: Consider implementing "lookback" merge policy
Key: LUCENE-5134
URL: https://issues.apache.org/jira/browse/LUCENE-5134
Project: Lucene - Core
Issue Type: Improvement
Reporter: Otis Gospodnetic
Priority: Minor
In
http://blog.mikemccandless.com/2011/02/visualizing-lucenes-segment-merges.html
Mike mentioned lookahead as something that could possibly yield more
optimal merges.
But what about lookback?
What if some sort of stats were kept about about which segments were
picked for merges? With some sort of stats in hand, could one look
back and, knowing what happened after those merges, evaluate if more
optimal merge choices could have been made and then use that "next
time"?
See http://search-lucene.com/m/D7ypz1gT2H91
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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
