Skip to content

knative-eventing: lower resource requests#26101

Merged
openshift-merge-robot merged 1 commit into
openshift:masterfrom
petr-muller:knative-cpus
Feb 10, 2022
Merged

knative-eventing: lower resource requests#26101
openshift-merge-robot merged 1 commit into
openshift:masterfrom
petr-muller:knative-cpus

Conversation

@petr-muller
Copy link
Copy Markdown
Member

knative-eventing requests are very high (OpenShift CI clusters' workers have 16CPUs so can basically fit just three Pods that request 4 CPUs) and its jobs spawn a lot of pods (mostly image builds). This causes massive scale-up events in OpenShift CI (easily 150+ instances) which are not actually necessary because the pods do not actually consume that many resources.

For some time, OpenShift CI has pod-scaler which automatically sets requests to a .8 quantile of the consumption peak of that workload if that value is higher than whatever is set in the ci-operator config, so lowering these resources should not result in any resource-related problems.

For example, the bin build of the release-next__48 builds is known to consume around 2.5CPU so that value would be dynamically set to that Pod.

/cc @mgencur @lberk @jupierce

@openshift-ci openshift-ci Bot requested review from jupierce, lberk and mgencur February 8, 2022 17:18
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 8, 2022
@petr-muller
Copy link
Copy Markdown
Member Author

/test pj-rehearse

1 similar comment
@pierDipi
Copy link
Copy Markdown
Member

pierDipi commented Feb 9, 2022

/test pj-rehearse

knative-eventing requests are very high (OpenShift CI clusters' workers have 16CPUs so can basically fit just three Pods that request 4 CPUs) and its jobs spawn a lot of pods (mostly image builds). This causes massive scale-up events in OpenShift CI (easily 150+ instances) which are not actually necessary because the pods do not actually consume that many resources.

For some time, OpenShift CI has [pod-scaler](https://resources.ci.openshift.org) which automatically sets requests to a .8 quantile of the consumption peak of that workload if that value is higher than whatever is set in the ci-operator config, so lowering these resources should not result in any resource-related problems.
@petr-muller
Copy link
Copy Markdown
Member Author

Retrying of infrastructure-failed builds (openshift/ci-tools#2659) kicked in, good

@pierDipi
Copy link
Copy Markdown
Member

pierDipi commented Feb 9, 2022

This seems related from https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_release/26101/rehearse-26101-pull-ci-openshift-knative-eventing-release-v1.1-47-e2e-aws-ocp-47/1491440007888506880:

the build knative-eventing-test-event-sender failed after 2m32s with reason OutOfMemoryKilled: The build pod was killed due to an out of memory condition.

@petr-muller
Copy link
Copy Markdown
Member Author

Yes, that's possible - the samples for that specific image build are a little all over the place but if they are consistently high then pod-scaler will learn the higher values over time. The retrying that landed today should help retrying these, too.

https://resources.ci.openshift.org/usage/builds?branch=release-v1.1&build=knative-eventing-test-event-sender&container=extract-image-content&org=openshift&repo=knative-eventing&variant=47

@pierDipi
Copy link
Copy Markdown
Member

/lgtm

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 10, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: petr-muller, pierDipi

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Feb 10, 2022
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 10, 2022

@petr-muller: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/rehearse/openshift/knative-eventing/release-v1.2/48-conformance-aws-ocp-48 07e9a126ca6168e7f84a97f2a48e35c1a70825e6 link unknown /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v1.1/49-reconciler-aws-ocp-49 07e9a126ca6168e7f84a97f2a48e35c1a70825e6 link unknown /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v1.1/49-conformance-aws-ocp-49 07e9a126ca6168e7f84a97f2a48e35c1a70825e6 link unknown /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v1.1/49-images 07e9a126ca6168e7f84a97f2a48e35c1a70825e6 link unknown /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v1.1/49-e2e-aws-ocp-49 07e9a126ca6168e7f84a97f2a48e35c1a70825e6 link unknown /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v1.0/49-e2e-aws-ocp-49 07e9a126ca6168e7f84a97f2a48e35c1a70825e6 link unknown /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v1.0/49-reconciler-aws-ocp-49 07e9a126ca6168e7f84a97f2a48e35c1a70825e6 link unknown /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v1.2/47-e2e-aws-ocp-47 07e9a126ca6168e7f84a97f2a48e35c1a70825e6 link unknown /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v1.1/48-e2e-aws-ocp-48 07e9a126ca6168e7f84a97f2a48e35c1a70825e6 link unknown /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v1.2/47-conformance-aws-ocp-47 07e9a126ca6168e7f84a97f2a48e35c1a70825e6 link unknown /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v1.2/47-images 07e9a126ca6168e7f84a97f2a48e35c1a70825e6 link unknown /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v1.0/49-images 07e9a126ca6168e7f84a97f2a48e35c1a70825e6 link unknown /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v1.1/48-conformance-aws-ocp-48 07e9a126ca6168e7f84a97f2a48e35c1a70825e6 link unknown /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v0.26/49-e2e-aws-ocp-49 01a00b4 link unknown /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v0.25/47-conformance-aws-ocp-47 07e9a126ca6168e7f84a97f2a48e35c1a70825e6 link unknown /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v0.26/48-conformance-aws-ocp-48 07e9a126ca6168e7f84a97f2a48e35c1a70825e6 link unknown /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v0.26/48-images 07e9a126ca6168e7f84a97f2a48e35c1a70825e6 link unknown /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v0.26/48-e2e-aws-ocp-48 07e9a126ca6168e7f84a97f2a48e35c1a70825e6 link unknown /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v1.1/47-e2e-aws-ocp-47 01a00b4 link unknown /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v0.25/47-reconciler-aws-ocp-47 07e9a126ca6168e7f84a97f2a48e35c1a70825e6 link unknown /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v0.26/48-reconciler-aws-ocp-48 07e9a126ca6168e7f84a97f2a48e35c1a70825e6 link unknown /test pj-rehearse
ci/prow/pj-rehearse 01a00b4 link false /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v1.0/47-e2e-aws-ocp-47 07e9a126ca6168e7f84a97f2a48e35c1a70825e6 link unknown /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v1.0/47-conformance-aws-ocp-47 07e9a126ca6168e7f84a97f2a48e35c1a70825e6 link unknown /test pj-rehearse
ci/rehearse/openshift/knative-eventing/release-v0.25/47-e2e-aws-ocp-47 07e9a126ca6168e7f84a97f2a48e35c1a70825e6 link unknown /test pj-rehearse

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@openshift-merge-robot openshift-merge-robot merged commit 76ba06f into openshift:master Feb 10, 2022
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 10, 2022

@petr-muller: Updated the ci-operator-misc-configs configmap in namespace ci at cluster app.ci using the following files:

  • key openshift-knative-eventing-release-next__47.yaml using file ci-operator/config/openshift/knative-eventing/openshift-knative-eventing-release-next__47.yaml
  • key openshift-knative-eventing-release-next__48.yaml using file ci-operator/config/openshift/knative-eventing/openshift-knative-eventing-release-next__48.yaml
  • key openshift-knative-eventing-release-v0.25__47.yaml using file ci-operator/config/openshift/knative-eventing/openshift-knative-eventing-release-v0.25__47.yaml
  • key openshift-knative-eventing-release-v0.25__48.yaml using file ci-operator/config/openshift/knative-eventing/openshift-knative-eventing-release-v0.25__48.yaml
  • key openshift-knative-eventing-release-v0.25__49.yaml using file ci-operator/config/openshift/knative-eventing/openshift-knative-eventing-release-v0.25__49.yaml
  • key openshift-knative-eventing-release-v0.26__47.yaml using file ci-operator/config/openshift/knative-eventing/openshift-knative-eventing-release-v0.26__47.yaml
  • key openshift-knative-eventing-release-v0.26__48.yaml using file ci-operator/config/openshift/knative-eventing/openshift-knative-eventing-release-v0.26__48.yaml
  • key openshift-knative-eventing-release-v0.26__49.yaml using file ci-operator/config/openshift/knative-eventing/openshift-knative-eventing-release-v0.26__49.yaml
  • key openshift-knative-eventing-release-v1.0__47.yaml using file ci-operator/config/openshift/knative-eventing/openshift-knative-eventing-release-v1.0__47.yaml
  • key openshift-knative-eventing-release-v1.0__48.yaml using file ci-operator/config/openshift/knative-eventing/openshift-knative-eventing-release-v1.0__48.yaml
  • key openshift-knative-eventing-release-v1.0__49.yaml using file ci-operator/config/openshift/knative-eventing/openshift-knative-eventing-release-v1.0__49.yaml
  • key openshift-knative-eventing-release-v1.1__47.yaml using file ci-operator/config/openshift/knative-eventing/openshift-knative-eventing-release-v1.1__47.yaml
  • key openshift-knative-eventing-release-v1.1__48.yaml using file ci-operator/config/openshift/knative-eventing/openshift-knative-eventing-release-v1.1__48.yaml
  • key openshift-knative-eventing-release-v1.1__49.yaml using file ci-operator/config/openshift/knative-eventing/openshift-knative-eventing-release-v1.1__49.yaml
  • key openshift-knative-eventing-release-v1.2__47.yaml using file ci-operator/config/openshift/knative-eventing/openshift-knative-eventing-release-v1.2__47.yaml
  • key openshift-knative-eventing-release-v1.2__48.yaml using file ci-operator/config/openshift/knative-eventing/openshift-knative-eventing-release-v1.2__48.yaml
  • key openshift-knative-eventing-release-v1.2__49.yaml using file ci-operator/config/openshift/knative-eventing/openshift-knative-eventing-release-v1.2__49.yaml
Details

In response to this:

knative-eventing requests are very high (OpenShift CI clusters' workers have 16CPUs so can basically fit just three Pods that request 4 CPUs) and its jobs spawn a lot of pods (mostly image builds). This causes massive scale-up events in OpenShift CI (easily 150+ instances) which are not actually necessary because the pods do not actually consume that many resources.

For some time, OpenShift CI has pod-scaler which automatically sets requests to a .8 quantile of the consumption peak of that workload if that value is higher than whatever is set in the ci-operator config, so lowering these resources should not result in any resource-related problems.

For example, the bin build of the release-next__48 builds is known to consume around 2.5CPU so that value would be dynamically set to that Pod.

/cc @mgencur @lberk @jupierce

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.

pierDipi added a commit to pierDipi/eventing that referenced this pull request Feb 14, 2022
See openshift/release#26101

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
openshift-merge-robot pushed a commit to openshift/knative-eventing that referenced this pull request Feb 14, 2022
See openshift/release#26101

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
openshift-cherrypick-robot pushed a commit to openshift-cherrypick-robot/knative-eventing that referenced this pull request Feb 14, 2022
See openshift/release#26101

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
openshift-cherrypick-robot pushed a commit to openshift-cherrypick-robot/knative-eventing that referenced this pull request Feb 14, 2022
See openshift/release#26101

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
openshift-cherrypick-robot pushed a commit to openshift-cherrypick-robot/knative-eventing that referenced this pull request Feb 14, 2022
See openshift/release#26101

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
openshift-cherrypick-robot pushed a commit to openshift-cherrypick-robot/knative-eventing that referenced this pull request Feb 14, 2022
See openshift/release#26101

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
openshift-cherrypick-robot pushed a commit to openshift-cherrypick-robot/knative-eventing that referenced this pull request Feb 14, 2022
See openshift/release#26101

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
openshift-merge-robot pushed a commit to openshift/knative-eventing that referenced this pull request Feb 14, 2022
See openshift/release#26101

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>

Co-authored-by: Pierangelo Di Pilato <pierdipi@redhat.com>
pierDipi added a commit to pierDipi/eventing-kafka-broker that referenced this pull request Feb 14, 2022
Same as:
openshift/knative-eventing@a94c97b

See openshift/release#26101

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
openshift-merge-robot pushed a commit to openshift-knative/eventing-kafka-broker that referenced this pull request Feb 14, 2022
Same as:
openshift/knative-eventing@a94c97b

See openshift/release#26101

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
openshift-cherrypick-robot pushed a commit to openshift-cherrypick-robot/eventing-kafka-broker that referenced this pull request Feb 14, 2022
Same as:
openshift/knative-eventing@a94c97b

See openshift/release#26101

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
openshift-cherrypick-robot pushed a commit to openshift-cherrypick-robot/eventing-kafka-broker that referenced this pull request Feb 14, 2022
Same as:
openshift/knative-eventing@a94c97b

See openshift/release#26101

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
openshift-merge-robot pushed a commit to openshift/knative-eventing that referenced this pull request Feb 14, 2022
See openshift/release#26101

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>

Co-authored-by: Pierangelo Di Pilato <pierdipi@redhat.com>
openshift-merge-robot pushed a commit to openshift-knative/eventing-kafka-broker that referenced this pull request Feb 14, 2022
Same as:
openshift/knative-eventing@a94c97b

See openshift/release#26101

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>

Co-authored-by: Pierangelo Di Pilato <pierdipi@redhat.com>
openshift-merge-robot pushed a commit to openshift/knative-eventing that referenced this pull request Feb 14, 2022
See openshift/release#26101

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>

Co-authored-by: Pierangelo Di Pilato <pierdipi@redhat.com>
openshift-merge-robot pushed a commit to openshift/knative-eventing that referenced this pull request Feb 15, 2022
See openshift/release#26101

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>

Co-authored-by: Pierangelo Di Pilato <pierdipi@redhat.com>
pierDipi added a commit to pierDipi/eventing-kafka-broker that referenced this pull request Feb 15, 2022
Same as:
openshift/knative-eventing@a94c97b

See openshift/release#26101

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
openshift-merge-robot pushed a commit to openshift-knative/eventing-kafka-broker that referenced this pull request Feb 15, 2022
Same as:
openshift/knative-eventing@a94c97b

See openshift/release#26101

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
openshift-cherrypick-robot pushed a commit to openshift-cherrypick-robot/eventing-kafka-broker that referenced this pull request Feb 15, 2022
openshift-merge-robot pushed a commit to openshift/knative-eventing that referenced this pull request Feb 15, 2022
See openshift/release#26101

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>

Co-authored-by: Pierangelo Di Pilato <pierdipi@redhat.com>
openshift-merge-robot pushed a commit to openshift-knative/eventing-kafka-broker that referenced this pull request Feb 15, 2022
Same as:
openshift/knative-eventing@a94c97b

See openshift/release#26101

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>

Co-authored-by: Pierangelo Di Pilato <pierangelodipilato@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants