search

kubernetes-sigs / descheduler

Descheduler for Kubernetes
https://sigs.k8s.io/descheduler
Apache License 2.0
4.48k stars 669 forks source link

Open workload datasets and benchmarking models #1002

Closed wisaaco closed 1 year ago

wisaaco commented 1 year ago

Hello,

I work in academia and I would like to evaluate some descheduler models but I have not found any workload real or emulated that can use for that purpose.

I hope not to bother with this question in this channel, but in many academic studies - the ones I have been able to read - the scenarios presented are relatively small. I would like to apply strategies on representative ecosystems and workloads and even devise some benchmarking models.

I welcome any suggestions in this regard.

Best regards, Isaac

a7i commented 1 year ago

Hi Iassc, What would the dataset contain? What would the benchmark model consist of?

wisaaco commented 1 year ago

Hello, We are working on a research project to improve job allocation and scheduling in Kubernetes-related computing infrastructures. Therefore, it would be ideal to have datasets where data on related problems (jobs, QoS needs, temporal metrics, allocation and scheduling decisions, etc.) are available. We intend to improve these algorithms to competitively improve current solutions (cost reduction, energy consumption, etc.) and also to be able to generate benchmarking models for evaluation or simulation in other ecosystems.

Best

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 1 year ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/descheduler/issues/1002#issuecomment-1555907834): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.