jpountz commented on issue #13883: URL: https://github.com/apache/lucene/issues/13883#issuecomment-3019865040
It looks like both options 1 and 2 try to dynamically update the number of merge threads based on multi-tenancy, option 1 does it from the outside via a manager, and option 2 from inside CMS. These 2 options sound quite complicated to me. I'd suggest creating a fresh new MergeScheduler that would schedule merges in a shared thread pool for all `IndexWriter`s? Merging activity would be controlled by the size of the thread pool (which is akin to CMS's maxThreadCount) and the max size of the queue (akin to CMS's maxMergeCount-maxThreadCount). It's simpler to me because the total merge activity is naturally capped globally, instead of requiring N-N feedback loops across ConcurrentMergeScheduler instances. It would also probably better scale with the number of `IndexWriter`s? -- 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
