Fly-Style commented on PR #20708: URL: https://github.com/apache/druid/pull/20708#issuecomment-6441655660
> Instead, a good intuitive alternative would be to reset the running average every time the scaling cooldown elapses. Then every (actionable) scale up or scale down decision is not polluted by old metrics even if taskDuration is much longer minScaleUpDelay or minScaleDownDelay. I fully agree with that statement, would love to see it. > But implementing that seems more complicated than necessary at the moment. May agree with that. > Once a taskCount has been chosen, commit to it and let it become stable. Here where my concern is risen. Do we want to commit to unlucky choice at the beginning, while the general design should be tied to [task amount] cost-efficiency? -- 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]
