Skip to content

(WIP) feat(scheduler): implement caching mechanism for inter-pod affinity#137310

Open
KunWuLuan wants to merge 1 commit intokubernetes:masterfrom
KunWuLuan:feat/interpodaffinity-cache
Open

(WIP) feat(scheduler): implement caching mechanism for inter-pod affinity#137310
KunWuLuan wants to merge 1 commit intokubernetes:masterfrom
KunWuLuan:feat/interpodaffinity-cache

Conversation

@KunWuLuan
Copy link
Contributor

@KunWuLuan KunWuLuan commented Feb 28, 2026

feat(scheduler): implement caching mechanism for inter-pod affinitynd topology spread plugins

Add comprehensive caching infrastructure to improve scheduling performance by reducing redundant computations for pod affinity and topology spread constraints. Introduces:

  • New cache plugin framework with generic caching interfaces
  • Dedicated caches for inter-pod affinity term processing
  • Topology spread constraint caching with score maps
  • Filtering optimization through cached pod metadata
  • Comprehensive test coverage for all caching components

This optimization significantly reduces CPU overhead during scheduling by memoizing expensive affinity and spread calculations, particularly beneficial for clusters with complex affinity rules and high scheduling throughput.

Performance improvements:

  • Reduced redundant namespace and label lookups
  • Cached topology key evaluations
  • Optimized pod matching algorithms
  • Improved scoring computation efficiency

What type of PR is this?

/kind feature

What this PR does / why we need it:

Which issue(s) this PR is related to:

#137306

Special notes for your reviewer:

Does this PR introduce a user-facing change?


Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


…nd topology spread plugins

Add comprehensive caching infrastructure to improve scheduling performance by reducing
redundant computations for pod affinity and topology spread constraints. Introduces:

- New cache plugin framework with generic caching interfaces
- Dedicated caches for inter-pod affinity term processing
- Topology spread constraint caching with score maps
- Filtering optimization through cached pod metadata
- Comprehensive test coverage for all caching components

This optimization significantly reduces CPU overhead during scheduling by
memoizing expensive affinity and spread calculations, particularly beneficial
for clusters with complex affinity rules and high scheduling throughput.

Performance improvements:
- Reduced redundant namespace and label lookups
- Cached topology key evaluations
- Optimized pod matching algorithms
- Improved scoring computation efficiency

Signed-off-by: KunWuLuan <kunwuluan@gmail.com>
@k8s-ci-robot
Copy link
Contributor

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Feb 28, 2026
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot
Copy link
Contributor

Hi @KunWuLuan. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Feb 28, 2026
@k8s-ci-robot k8s-ci-robot added sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Feb 28, 2026
@github-project-automation github-project-automation bot moved this to Needs Triage in SIG Scheduling Feb 28, 2026
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: KunWuLuan
Once this PR has been reviewed and has the lgtm label, please assign macsko for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

Status: Needs Triage

Development

Successfully merging this pull request may close these issues.

2 participants