chore: Use self-affinity to ensure all pods schedule

[jonathan-innis]

Fixes #N/A

Description

Use self-affinity to ensure that all pods schedule when executing the scheduling benchmark. This also expands the test case to run up to 20,000 pods since the tests are executing quicker now

Scheduling Benchmark

=== RUN   TestSchedulingProfile
scheduled 40151 against 8031 nodes in total in 59.075917891s 679.6508870853593 pods/sec
400 instances 1 pods      1 nodes     183.429µs per scheduling      183.429µs per pod
400 instances 50 pods     10 nodes    42.179802ms per scheduling    843.596µs per pod
400 instances 100 pods    20 nodes    93.097613ms per scheduling    930.976µs per pod
400 instances 500 pods    100 nodes   415.767736ms per scheduling   831.535µs per pod
400 instances 1000 pods   200 nodes   890.825521ms per scheduling   890.825µs per pod
400 instances 1500 pods   300 nodes   1.300125958s per scheduling   866.75µs per pod
400 instances 2000 pods   400 nodes   1.625429875s per scheduling   812.714µs per pod
400 instances 5000 pods   1000 nodes  5.086005208s per scheduling   1.017201ms per pod
400 instances 10000 pods  2000 nodes  12.071574167s per scheduling  1.207157ms per pod
400 instances 20000 pods  4000 nodes  35.739747083s per scheduling  1.786987ms per pod
--- PASS: TestSchedulingProfile (66.78s)
PASS

How was this change tested?

go test -bench=.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[rschalo]

Nice!

[rschalo]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jonathan-innis, rschalo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jonathan-innis]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[rschalo]

/lgtm