cxxiii opened a new issue, #3671: URL: https://github.com/apache/amoro/issues/3671
### Search before asking - [x] I have searched in the [issues](https://github.com/apache/amoro/issues?q=is%3Aissue) and found no similar issues. ### What would you like to be improved? Refine the definition of configuration parameter Quota and the calculation of metric Occupation—as well as improving the current self-optimizing scheduling policy based on Quota. ### How should we improve? 1. To ensure a reasonable allocation of optimizer resources among tables, optimize the configuration parameter Quota, which specifies the maximum number of optimizer resources that can be allocated to each table. Quota is defined as an integer value representing the upper limit of optimizer threads permitted for a single table. 2. Calculate Occupation as the ratio of the actual execution time of optimizer threads used by a table to its Quota execution time within the QUOTA_LOOK_BACK_TIME window. 3. When using the Quota-based scheduling strategy, continue to prioritize tables with the lowest Occupation. However, when an optimizer polls a task from the highest-priority table, it first checks whether the table’s current resource usage is below its Quota. If not, the optimizer proceeds to poll a task from the next table in the priority order. ### Are you willing to submit PR? - [x] Yes I am willing to submit a PR! ### Subtasks _No response_ ### 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
