gianm commented on PR #18493: URL: https://github.com/apache/druid/pull/18493#issuecomment-3268160445
> @gianm , it makes sense to reduce the number of netty worker threads since these threads mostly sit idle most of the time. > > But I wonder if the change is not too drastic, especially since this affects all services. e.g. even for a machine with 16 cpus, we are halving the value from 49 to 25, which can affect say an Overlord communicating with a large number of streaming tasks. > > Do you think it would make sense to maybe roll this out gradually, like have a formula which reduces the 49 to say 40-ish and decrease the values further in subsequent Druid releases? I believe the Netty worker threads are only supposed to be running callbacks, so they should need to scale with number of CPUs rather than number of outgoing connections. For that reason I am not expecting the smaller pools to be a bottleneck & I would rather jump straight to a new formula. Maybe we can validate this with some scale testing prior to release? -- 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]
