jadami10 opened a new issue, #8928: URL: https://github.com/apache/pinot/issues/8928
When the user does not specify the number of threads for a query, the CombinePlan* operators both use a minimum of 1 threads, maximum of 10 threads, and a default of num_cpus/2 threads for their tasks. The GroupByOrderByCombineOperator on the other hand just sets the number of threads to the number of operators. I haven't actually profiled this or logged how many operators there are in practice, but this feels like it could be a bug when comparing to how the CombinePlan code treats this flag. I'm curious if you feel this is of concern as well before we dig into it further. -- 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: commits-unsubscr...@pinot.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org