[proposal]How to rationally Evict pods so that high-load node utilization reaches a reasonable level

[LY-today]

What is your proposal:
When descheduler evaluates which pod to expel to reduce the utilization of high-load nodes to a reasonable level, can descheduler perform matching calculations on the actual usage of the pod and the amount of eviction resources in advance?

Why is this needed:
This can reduce the number of times a single node is repeatedly entered into the eviction logical unit, reduce the number of single node eviction instances, and indirectly improve the accuracy of the eviction results and the stability of the business while ensuring that hot issues are solved.

Is there a suggested solution, if so, please add it:
evict pod priority selector：podNowResourceUsages >= nodeNowResourceUsages - nodeHighResourceThresholds * nodeResourceAllocatable

ps：If the community approves the proposal, I can provide PR

[wzzcocoon]

This proposal is very good, it solves my problems and troubles.

[mangk]

This proposal is very good, it solves my problems and troubles.

Fully agree

[eahydra]

Yes, it looks good to me. I checked the "evictPodsFromSourceNodes" function in descheduler's plugin LowNodeLoad and found some cases that need to be optimized, including the one you mentioned.
Feel free to contribute. @LY-today