capistrant commented on PR #12571: URL: https://github.com/apache/druid/pull/12571#issuecomment-1178199675
> Thanks for the review @capistrant I found this blog - https://metamarkets.com/2016/impact-on-query-speed-from-forced-processing-ordering-in-druid/ - that talked about the concerns mentioned by the implementer. > > I think if we call out this change in the release notes, then operators with heterogeneous workloads can change this setting if they have long running queries mixed in with hot queries. From the blog: So the lesson learned here is when there is a large backlog of work, having orderly execution helps everything get through in a predictable manner. However, when speed and nimbleness are key, let chaos reign. This note makes me sway back to keeping this configuration disabled by default. If enabling hurt the interactive query performance of a prod cluster, it would make me think twice about enabling by default. However the blog is from 2016 and the druid version was 0.9 at the time. Perhaps there is a need to re-create that study with current Druid to see if the results tell the same story. For now, I will have to revoke the approval out of doubt about this after reading the blog. -- 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]
