[GitHub] [pinot] Jackie-Jiang commented on issue #8928: GroupByOrderByCombineOperator does not bound the number of threads it uses

[GitBox <gi...@apache.org>]

Jackie-Jiang commented on issue #8928:
URL: https://github.com/apache/pinot/issues/8928#issuecomment-1160768350

   This is a legacy behavior which is carried over to prevent performance regression. Basically for group-by queries, we will use all CPU resources if not explicitly configured. `maxExecutionThreads` query option will still be honored if specified.
   
   It is a trade off between latency and stability: using all CPU cores can give the best latency if query rate is low, but one expensive query can exhaust the CPU resource.
   
   There might be a way to get both world. We may dynamically decide the threads to use based on the query load. I think this is a topic worth more discussion. cc @kishoreg @siddharthteotia @yupeng9 


-- 
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-unsubscribe@pinot.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org