Tracking issue for issues related to scheduler performance/scalability

[davidopp]

Benchmarking-related

• Scheduler Performance Testing Proposal Scheduler Performance Testing Proposal #18091
• Add a couple of benchmarks for the scheduler Add a couple of benchmarks for the scheduler #17415
• Design a mechanism to record a real workload and replay it deterministically Design a mechanism to record a real workload and replay it deterministically #3138

Performance/scalability improvement ideas

• Relaxed randomization scheduler: Relaxed randomization #18414
• Equivalence classes and caching Implement "equivalence classes" and caching thereof #17390
• Parallelizing predicate and priority functions across machines Parallelize evaluation of predicate and priority functions for a single pod across machines #17389

(If I forgot any, please add them. If you do a PR related to scheduler performance/scalability improvements, it's not necessary to add it to the list if it's not already on the list, but please try to remember to mention this issue number so it shows up in the issue log).

[davidopp]

@kubernetes/rh-scalability @kubernetes/sig-scalability @jbeda @xiang90 @hongchaodeng

[wojtek-t]

@gmarek /me

[kevin-wangzefeng]

/cc @HardySimpson

[HaiyangDING]

cc @HaiyangDING @hurf

[timothysc]

cc @rrati

[davidopp]

ref/ #18831 (which mentions a bunch of issues/PRs)
ref/ #18458

[davidopp]

@kubernetes/huawei

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[timchenxiaoyu]

/reopen

[k8s-ci-robot]

@timchenxiaoyu: you can't re-open an issue/PR unless you authored it or you are assigned to it.

In response to this:

/reopen

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/test-infra repository.