Skip to content

Commit b9b3432

Browse files
committed
chore: add a note about jailer performance scaling
Jailer startup time is dependent on the number of mount points in the system and number of jailers starting in parallel. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
1 parent 8e72870 commit b9b3432

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

docs/jailer.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -279,6 +279,14 @@ Note: default value for `<api-sock>` is `/run/firecracker.socket`.
279279

280280
### Known limitations
281281

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

0 commit comments

Comments
 (0)