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

Create a Podman performance tips tutorial #14902

Closed
eriksjolund opened this issue Jul 12, 2022 · 3 comments · Fixed by #14903
Closed

Create a Podman performance tips tutorial #14902

eriksjolund opened this issue Jul 12, 2022 · 3 comments · Fixed by #14903
Labels
kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@eriksjolund
Copy link
Contributor

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind feature

Description

Add a Podman tutorial that discusses factors that might impact the speed of Podman.

Some sketchy ideas:

  • use --uidmap and --gidmap instead of the --volume option :U
  • use :O to avoid local disk
  • use a fast OCI runtime (crun)
  • use a fast storage driver (native overalyfs)
  • reuse the package repository cache with an overlay mount when building container images
  • network performance for rootless Podman
    • slirp4netns comes with a performance penalty
    • use socket activation to avoid slirp4netns
    • maybe use rootful Podman with --user $user (where $user != 0) to avoid slirp4netns
  • choosing a host file system (is reflink support important?)
  • whether to use the podman run option --new
  • use smaller container images
  • lazy pulling of container images
  • benchmark tip: create a separate account with sudo useradd testuser && sudo machinectl testuser@
@openshift-ci openshift-ci bot added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 12, 2022
@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@afbjorklund
Copy link
Contributor

afbjorklund commented Sep 25, 2022

Or maybe "use root" ? 😀

At least it could be interesting to at least mention the cost of rootless, when discussing the mitigations ?

Preferably with some benchmarks.

@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 10, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants