This repository was archived by the owner on Oct 9, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 23
Comments
[wip] FairQ: An implementation of K8s Workqueue#21
Open
Conversation
- The implementation aims to provide equal worker allocation across all namespaces. This avoids one namespace from taking over all workers and thus increasing the latency to process a namespace with lower load. - The queue is thus fair for every namespace. IF somenamespace has skewed work duration (larger) then it will not inversely impact the reconcilation latency for objects in another namespace TODO: metrics support
@kumare3
kumare3
requested review from
EngHabu,
katrogan and
wild-endeavor
as code owners
June 6, 2019 21:34
@kumare3
kumare3
changed the title
(削除) FairQ: An implementation of K8s Workqueue (削除ここまで)
(追記) [wip] FairQ: An implementation of K8s Workqueue (追記ここまで)
May 27, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
namespaces. This avoids one namespace from taking over all workers and
thus increasing the latency to process a namespace with lower load.
skewed work duration (larger) then it will not inversely impact the
reconcilation latency for objects in another namespace
TODO: workqueue metrics support