Skip to content
This repository was archived by the owner on Oct 9, 2023. It is now read-only.

Conversation

@kumare3
Copy link
Contributor

@kumare3 kumare3 commented Jun 6, 2019

  • 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: workqueue metrics support

 - 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 changed the title FairQ: An implementation of K8s Workqueue [wip] FairQ: An implementation of K8s Workqueue May 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants