Skip to content

chore: add a note about jailer performance scaling #5383

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Aug 15, 2025
Merged

chore: add a note about jailer performance scaling #5383

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3a3c19c
chore: add a note about jailer performance scaling
ShadowCurse Aug 14, 2025
8f0e2a8
Merge branch 'main' into jailer_doc
Manciukic Aug 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/jailer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -279,6 +279,14 @@ Note: default value for `<api-sock>` is `/run/firecracker.socket`.

### Known limitations

- The time it takes to create a jail depends on the number of mount points in
the system and the number of jailers starting at the same time. Due to the
number of mount points playing a bigger role in jailer slowdown, it is
recommended to keep the number of mount points in a system to a minimum. The
approximate slowdown of the jail creation time is:
- 2x when 10 jails are created in parallel with 0 mount points in the system
- 10x when 10 jails are created in parallel with 500 mount points in the
system.
- When passing the --daemonize option to Firecracker without the --new-ns-pid
option, the Firecracker process will have a different PID than the Jailer
process and killing the Jailer will not kill the Firecracker process. As a
Expand Down