Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolution of preemption_victims metric is limiting #112912

Closed
alculquicondor opened this issue Oct 7, 2022 · 9 comments
Closed

Resolution of preemption_victims metric is limiting #112912

alculquicondor opened this issue Oct 7, 2022 · 9 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@alculquicondor
Copy link
Member

alculquicondor commented Oct 7, 2022

What would you like to be added?

Have better resolution of the metric. The range is probably good (0 to 50), but the resolution is not very useful. Maybe it should be an exponential scale instead of linear

Buckets: metrics.LinearBuckets(5, 5, 10),

Why is this needed?

We should have more visibility around average number of preemptions. It's not possible to see if pods require less than 5 preemptions to inform how expensive preemption is for a certain QPS.

@alculquicondor alculquicondor added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 7, 2022
@k8s-ci-robot k8s-ci-robot added needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 7, 2022
@alculquicondor
Copy link
Member Author

/sig scheduling
/sig instrumentation

@logicalhan is the proposal backwards compatible? The guide is not very clear about changing the buckets, but I seem to remember it's ok to change them
https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/metric-stability.md#stable

@k8s-ci-robot k8s-ci-robot added sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Oct 7, 2022
@logicalhan
Copy link
Member

/sig scheduling /sig instrumentation

@logicalhan is the proposal backwards compatible? The guide is not very clear about changing the buckets, but I seem to remember it's ok to change them https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/metric-stability.md#stable

Changing buckets is fine actually.

@lengrongfu
Copy link
Contributor

lengrongfu commented Oct 8, 2022

Can I work for this issue?If there is a better option, feel free to unassign. @alculquicondor

@lengrongfu
Copy link
Contributor

/assign

@pacoxu
Copy link
Member

pacoxu commented Oct 11, 2022

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 11, 2022
@lengrongfu
Copy link
Contributor

/close

@k8s-ci-robot
Copy link
Contributor

@lengrongfu: You can't close an active issue/PR unless you authored it or you are a collaborator.

In response to this:

/close

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.

@pacoxu
Copy link
Member

pacoxu commented Oct 14, 2022

/close

If you set Fixes #112912 correctly, this issue will be closed automatically by GitHub. There is an extra # in #112939 (comment).

@k8s-ci-robot
Copy link
Contributor

@pacoxu: Closing this issue.

In response to this:

/close

If you set Fixes #112912 correctly, this issue will be closed automatically by GitHub. There is an extra # in #112939 (comment).

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

5 participants