Make the process of `calculateRequirementsForAssignments` parallel. about kueue

[denkensk]

/cc @ahg-g @alculquicondor
/assign @denkensk

[k8s-triage-robot]

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

This bot triages issues and PRs 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:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[alculquicondor]

/lifecycle frozen

[alculquicondor]

This should be simple enough

/help

[k8s-ci-robot]

@alculquicondor:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

This should be simple enough

/help

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.

[kannon92]

Hello! I'm interested in pulling this issue.

I think the code changed a bit since this was posted.

Is

kueue/pkg/scheduler/scheduler.go

Line 185 in 6eeb73b

func (s *Scheduler) nominate(ctx context.Context, workloads []workload.Info, snap cache.Snapshot) []entry {

this the code that we want to run in parallel now?

[ahg-g]

Thanks Kevin and welcome to Kueue :)

Until we create scalability tests to understand where the bottlenecks are, this issue may not be a priority.

But another issue that needs some attention is #259; would you be interested in that one?

[kannon92]

Yea, that sounds great! And thank you!

I've been attending the calls for the working group so I'm interested in helping out where I can.

[ahg-g]

Sounds good, feel free to assign it to yourself, for some reason I can't.

[alculquicondor]

@kannon92 any progress on this?

[kannon92]

I have made 0 progress on this.

[alculquicondor]

Should we leave it open for other contributors or can you still handle it?

[kannon92]

Yea, anyone who is interested should feel free to take it.

[alculquicondor]

/help

[kannon92]

/unassign @denkensk

[alculquicondor]

/close

So far the biggest bottlenecks in Kueue have been the API calls, which @gabesaba optimized.

I don't think we need to introduce parallel computations yet.

EDIT: using locks could even cause performance regressions.

[k8s-ci-robot]

@alculquicondor: Closing this issue.

In response to this:

/close

So far the biggest bottlenecks in Kueue have been the API calls, which @gabesaba optimized.

I don't think we need to introduce parallel computations yet.

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-sigs/prow repository.