Thanks for showing I wasn't completely crazy to think this made sense, Mike.
I added:
https://issues.apache.org/jira/browse/LUCENE-5134
https://issues.apache.org/jira/browse/LUCENE-5135
Otis
On Mon, Jul 15, 2013 at 1:28 PM, Michael McCandless
luc...@mikemccandless.com wrote:
Lookback is a
Lookback is a good idea: you could at least gather statistics and
assess, later, whether good merges had been selected, and maybe play
what if games to explore if different merge selections would have
resulted in less copying.
A time-based MergeScheduler would make sense: e.g., it would allow
Hi,
I was (re-re-re-re)-reading Mike's post about Lucene segment merges -
http://blog.mikemccandless.com/2011/02/visualizing-lucenes-segment-merges.html
Mike mentioned lookhead as something that could possibly yield more
optimal merges.
But what about lookback? :)
What if some sort of stats