jpountz opened a new issue, #12068:
URL: https://github.com/apache/lucene/issues/12068
### Description
Our current merge throttling implementation also covers the creation of the
compound file when `MergePolicy#useCompoundFile` returns true. But I don't
think it is right and I suspect that it was not done intentionally:
- My understanding is that merge throttling does not generally try to
throttle I/O, e.g. integrity checks are not throttled. It mostly uses written
bytes as a best-effort proxy for the amount of CPU spent on merging, so that
merges leave CPU for searches.
- The page cache has protection against long sequential reads/writes from
completely trashing the filesystem cache.
@mikemccand Do you know if this was intentional?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
