Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CapMan visibility] sets throttle policy correctly #6088

Merged
merged 1 commit into from
Jul 3, 2024

Conversation

xurui-c
Copy link
Member

@xurui-c xurui-c commented Jul 2, 2024

The throttle policy should be the policy with the smallest number of threads. The existing logic simply takes the last throttling policy in the for-loop

@xurui-c xurui-c requested a review from a team as a code owner July 2, 2024 22:50
policy_name=allocation_policy.config_key(),
)
if allowance.max_threads < num_threads:
throttle_quota_and_policy = _QuotaAndPolicy(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this basically saying to set some sort of query throttling if we want to allocate a lower max threads ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

exactly

@xurui-c xurui-c requested a review from ayirr7 July 2, 2024 23:01
@xurui-c xurui-c merged commit 2cd5cc1 into master Jul 3, 2024
29 checks passed
@xurui-c xurui-c deleted the rachel/fixThrottlePolicyLogic branch July 3, 2024 17:54
kneeyo1 added a commit that referenced this pull request Jul 8, 2024
This reverts commit 2cd5cc1.
kneeyo1 added a commit that referenced this pull request Jul 8, 2024
kneeyo1 added a commit that referenced this pull request Jul 8, 2024
xurui-c added a commit that referenced this pull request Aug 13, 2024
…a when multiple throttle policies present (#6192)

Redo of #6088 because it got
reverted

Let's say the list of allocation policies that validates a query is
[Policy1, Policy2, Policy3]. Suppose Policy2 throttles the query with 2
threads, and Policy3 throttles the query with 3 threads.

The current logic will incorrectly say that the query is throttled by
the last policy in the list (Policy3) with the minimum allocated threads
across all policies in the list (2 threads).

This PR correctly sets the query to run with 2 threads as throttled by
Policy2

Co-authored-by: Rachel Chen <rachelchen@PL6VFX9HP4.attlocal.net>
@xurui-c xurui-c changed the title sets throttle policy correctly [CapMan visibility] sets throttle policy correctly Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants