Skip to content

Commit

Permalink
Merge pull request #20794 from eriksjolund/document-sometimes-slow-na…
Browse files Browse the repository at this point in the history
…tive-overlayfs

[CI:DOCS] performance: document sometimes slow native overlayfs
  • Loading branch information
openshift-merge-bot[bot] authored Nov 29, 2023
2 parents 5ab4513 + 13e5488 commit e14d095
Showing 1 changed file with 18 additions and 0 deletions.
18 changes: 18 additions & 0 deletions docs/tutorials/performance.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,24 @@ The following storage drivers are listed from fastest to slowest:
2. fuse-overlayfs
3. vfs

There is one notable exception to this speed ranking.
Creating a container takes significantly longer with _native overlayfs_ than _fuse-overlayfs_
when these conditions are all met:

* rootless Podman is used
* a modified UID/GID mapping is used
* _native overlayfs_ is used
* no container has yet been created with the specified container image and UID/GID mapping

Runtime speed is not affected. Only __podman create__ and the container creation phases of
__podman run__ and __podman build__ are affected.
For more details, see [GitHub comment](https://github.com/containers/podman/issues/16541#issuecomment-1352790422).
Command-line options that modify the UID/GID mapping are for example __--userns__, __--uidmap__ and __--gidmap__.
The command-line option `--userns auto` is particularly affected by this performance penalty,
because different UID/GID mappings could potentially be used on each invocation. For other uses of
__--userns__, __--uidmap__ and __--gidmap__ the performance penalty is a one-time cost
that only occurs the first time the command is run.

Using native overlayfs as an unprivileged user is only available for Podman version >= 3.1 on a Linux kernel version >= 5.12.

To show the current storage driver
Expand Down

0 comments on commit e14d095

Please sign in to comment.