Skip to content

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

Open
JeromeJaggi wants to merge 1 commit into
prod-stagingfrom
jeromejaggi/docs-snapshot-core
Open

docs(snapshots): Note compressed and incremental snapshot behavior#132
JeromeJaggi wants to merge 1 commit into
prod-stagingfrom
jeromejaggi/docs-snapshot-core

Conversation

@JeromeJaggi

Copy link
Copy Markdown
Member

Summary

Add a short section to the public Snapshots feature page describing two user-visible properties of the v0.9 snapshotting core:

  • Compression by default — keeps standby disk footprint small
  • Incremental capture after the first snapshot — later scale-to-zero cycles only capture changed memory/state

What's intentionally not in this PR

The deeper architectural changes from the v0.9 update (copy-on-write checkpointing, sync vs. async snapshot modes, VMM-fork mechanism) are operator-internal concerns and aren't appropriate for the public docs. Those will go to the enterprise docs in a separate PR.

Verification

  • `make lint` passes 0/0/0 on the modified file.
  • Branched from latest `prod-staging`.

Risk flag

The user-visible claims here ("compressed by default", "incremental after first") are based on the v0.9 platform team update slides. If the actual user-visible defaults differ — for example, if compression requires a flag, or if incremental behavior is gated on something else — please flag during review.

Audit reference

Item #1 (new snapshotting core) from the v0.9 docs audit, public-docs scope.


This PR was created by an AI agent.

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 <jerome@unikraft.io>
@JeromeJaggi JeromeJaggi temporarily deployed to pull-requests April 30, 2026 08:41 — with GitHub Actions Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant