From cf238956146329a5b4aaebc5e5c7f7c44d498f82 Mon Sep 17 00:00:00 2001 From: Jerome Jaggi Date: Thu, 30 Apr 2026 10:40:57 +0200 Subject: [PATCH] docs(snapshots): Note compressed and incremental snapshot behavior Add a short section explaining that snapshots are now compressed by default and incremental after the first capture. The first scale-to-zero cycle pays the full cost; later cycles only capture changed memory and state, making subsequent suspend/resume cheaper and faster. Signed-off-by: Jerome Jaggi --- pages/features/snapshots.mdx | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/pages/features/snapshots.mdx b/pages/features/snapshots.mdx index 1e7256e8..3c550cb4 100644 --- a/pages/features/snapshots.mdx +++ b/pages/features/snapshots.mdx @@ -61,6 +61,17 @@ Next, when traffic arrives, Unikraft Cloud brings up the app including its saved This ensures statefulness across scale-to-zero and scale-to-one cycles. It also eliminates long initialization times from heavyweight apps. +## Compressed and incremental snapshots + +The platform compresses every snapshot by default, which keeps the on-disk footprint of standby instances small. + +Snapshots are also **incremental**: after the first snapshot for an instance, the platform only captures the memory and state that have changed since the previous snapshot. +The first scale-to-zero cycle for a given instance runs the full snapshot path. +Later cycles are cheaper and faster because the platform reuses the unchanged data from earlier captures. + +You don't need to configure any of this. +The behavior is on by default and applies to every stateful scale-to-zero instance. + ## Learn more