jpountz commented on issue #13349: URL: https://github.com/apache/lucene/issues/13349#issuecomment-2101365494
Lucene already has a model for indexing/flushing concurrency that consists of indexing documents from multiple threads. I guess that the idea that you are suggesting could make sense when the indexing rate is low, so it can't use all resources, and you'd like to use these unused resources to decrease flushing latency. But if your indexing rate is low, flushing shouldn't be slow unless you very rarely reopen? So I'm not sure if this would fix an actual problem. For merging, it's a bit more compelling as things like force-merging were completely single-threaded before the changes that you listed, despite potentially taking a very long time. -- 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
