Skip to content

docs(snapshots): Note compressed and incremental snapshot behavior #132

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

Open
JeromeJaggi wants to merge 1 commit into
base: prod-staging
Choose a base branch
from
Open

docs(snapshots): Note compressed and incremental snapshot behavior #132

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
11 changes: 11 additions & 0 deletions pages/features/snapshots.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Loading