mikemccand commented on issue #13883: URL: https://github.com/apache/lucene/issues/13883#issuecomment-3039629342
OK I like these tradeoffs -- +1 to a new `MergeScheduler` with a fixed thread pool, and starting simple (no intelligence about being "fair" when writers are asking for too much merging overall). And applying backpressure to indexing threads (that keep producing more work for merging (the newly flushed segments)) when merging cannot keep up. There is also the thread pool for concurrent HNSW merging (within a single merge) -- apps could also use the same thread pool (as indexing and merging) for that, maybe. -- 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: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
