Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CI:DOCS] hack/perf/bz-2162111.sh: use custom network #17335

Merged

Conversation

vrothberg
Copy link
Member

Create the containers with a custom network. It has an impact on the speed of container creation.

Signed-off-by: Valentin Rothberg vrothberg@redhat.com

@baude @edsantiago PTAL

Does this PR introduce a user-facing change?

None

@openshift-ci openshift-ci bot added release-note-none approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Feb 2, 2023
Comment on lines 15 to 18
$ENGINE_A network rm -f $network_name >> /dev/null || true
$ENGINE_B network rm -f $network_name >> /dev/null || true
$ENGINE_A network create $network_name >> /dev/null
$ENGINE_B network create $network_name >> /dev/null
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason to not use random names? That would prevent all name conflicts.

Also I am missing where you remove the network after the test is done?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason to not use random names? That would prevent all name conflicts.

Easier debugging to know where it came from.

Also I am missing where you remove the network after the test is done?

I didn't intend to since it'll get remove on the next invocation. The other scripts may also leave containers etc. in storage.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm with @Luap99 on this one. It is polite to clean up after oneself.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't like leaking test resources for no reason.
I expected all test to cleanup what they created, I understand keeping images because pulling is expensive but the rest not so much.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please note the ./hack , it's not in ./test. I am not arguing against any of these points but ask to apply different standards to these hacked scripts.

I'll repush with cleaning up nonetheless 👍

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated. Added a commit on top to also clean up after the other benchmarks.

Create the containers with a custom network.  It has an impact on the
speed of container creation.

Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
To leave not leave some artifacts arounds.

Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
@rhatdan
Copy link
Member

rhatdan commented Feb 3, 2023

LGTM

@vrothberg
Copy link
Member Author

@giuseppe PTAL

Copy link
Member

@giuseppe giuseppe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 6, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 6, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: giuseppe, vrothberg

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:

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

@openshift-merge-robot openshift-merge-robot merged commit 3464df2 into containers:main Feb 6, 2023
@vrothberg vrothberg deleted the hack/perf/bz-2162111.sh branch February 6, 2023 12:41
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 11, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. release-note-none
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants