knative / eventing

Event-driven application platform for Kubernetes
https://knative.dev/docs/eventing
Apache License 2.0
1.39k stars 582 forks source link

Event Prioritization #5535

Open Spenhouet opened 3 years ago

Spenhouet commented 3 years ago

Problem Given many events of the same type but for example for different groups. The group could be anything provided by the event producer e.g. a customer.

In our specific use-case we are limited by hardware resources (GPUs specifically). There might be 1000 requests by group 1 and only 10 requests by group 2. We would like the ability to apply some fairness factor so that group 2 will be scheduled with a higher priority than group 1.

Additional context (optional)

I'm not sure if something like this already exists. Kubernetes seems to have something in this direction: Pod Priority and Preemption If this does not exist yet, then I would like to make this a feature request.

It is also open where the interface for this is. Such a fairness factor could be automatically calculated and managed by Knative but could also just be provided by the event producer.

github-actions[bot] commented 2 years ago

This issue is stale because it has been open for 90 days with no activity. It will automatically close after 30 more days of inactivity. Reopen the issue with /reopen. Mark the issue as fresh by adding the comment /remove-lifecycle stale.

lionelvillard commented 2 years ago

/remove-lifecycle stale

github-actions[bot] commented 2 years ago

This issue is stale because it has been open for 90 days with no activity. It will automatically close after 30 more days of inactivity. Reopen the issue with /reopen. Mark the issue as fresh by adding the comment /remove-lifecycle stale.

Spenhouet commented 2 years ago

/reopen /remove-lifecycle stale

knative-prow-robot commented 2 years ago

@Spenhouet: Reopened this issue.

In response to [this](https://github.com/knative/eventing/issues/5535#issuecomment-1017492325): >/reopen >/remove-lifecycle stale 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.
lionelvillard commented 2 years ago

/triage accepted

github-actions[bot] commented 1 week ago

This issue is stale because it has been open for 90 days with no activity. It will automatically close after 30 more days of inactivity. Reopen the issue with /reopen. Mark the issue as fresh by adding the comment /remove-lifecycle stale.