killxdcj opened a new issue #7066: URL: https://github.com/apache/incubator-doris/issues/7066
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/incubator-doris/issues?q=is%3Aissue) and found no similar issues. ### Description When schedule ScanNode, the current strategy will schedule scannodes to as many backends as possible, which can efficiently utilize cluster resources and improve query performance. However, for high throughput point query scenarios, the current scheduling strategy has some problems 1. Point query itself does not require many resources, so it is of little significance to mobilize all backends to serve query. 2. The thundering herd will be serious, which will affect the query performance and query parallelism of the cluster 3. It will increase the RPC and data interaction between backends, which will have a great impact on the performance Therefore, maybe we should support a new scheduling strategy for high-throughput point query scenarios, select as few backends as possible to serve query. ### Use case Suppose you have a table with many partitions, and the query scenario is high-throughput point query (each query will specify the distribute key) ### Related issues _No response_ ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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...@doris.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org For additional commands, e-mail: commits-h...@doris.apache.org
