/kind feature
/assign
/sig scheduling

---

We don't have any observability around event handling (= requeueing) throughput. Adding observability can be a monitor for a degradation around it. 
Also, based on the metric we add, we can find how fast event handling should be on a certain large scale, like we have 300 pods/s target in scheduling throughput. And then we may or may not need to improve the event handling throughput accordingly.

- [x]  1. Add an observability for event handling throughput. https://github.com/kubernetes/kubernetes/pull/125929
- [ ]  2. Benchmark and decide the ideal throughput.
- [ ]  3. Improve the throughput based on (2). (possible actions: simplify slower QHint(s), etc)


### Reference

- spown from the discussion in https://github.com/kubernetes/kubernetes/issues/124384
- general QHint issue: https://github.com/kubernetes/kubernetes/issues/118893



Scheduler: Observe/Improve event handling throughput 
This is a GitHub Issue
repo:kubernetes
owner:kubernetes
Title : Scheduler: Observe/Improve event handling throughput 
Issue date:

--- start body ---
/kind feature
/assign
/sig scheduling

---

We don't have any observability around event handling (= requeueing) throughput. Adding observability can be a monitor for a degradation around it. 
Also, based on the metric we add, we can find how fast event handling should be on a certain large scale, like we have 300 pods/s target in scheduling throughput. And then we may or may not need to improve the event handling throughput accordingly.

- [x]  1. Add an observability for event handling throughput. https://github.com/kubernetes/kubernetes/pull/125929
- [ ]  2. Benchmark and decide the ideal throughput.
- [ ]  3. Improve the throughput based on (2). (possible actions: simplify slower QHint(s), etc)


### Reference

- spown from the discussion in https://github.com/kubernetes/kubernetes/issues/124384
- general QHint issue: https://github.com/kubernetes/kubernetes/issues/118893



--- end body ---
