[GH-ISSUE #12] P2P snapshot distribution #7

New issue

Open

opened 2026-10-29 14:18:18 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-29 14:18:18 +00:00

Owner

Originally created by @yingdi-shan on GitHub (Jul 27, 2026).
Original GitHub issue: https://github.com/kvcache-ai/AgentENV/issues/12

Originally assigned to: @LSX-s-Software on GitHub.

Motivation

A key driver for P2P distribution is efficient snapshotting (checkpoint). With centralized storage, the snapshot publish path must upload potentially large artifacts (memory + disk checkpoints) to the remote store before the operation is considered complete. This upload latency blocks the snapshot call and limits how fast checkpoints can be taken. With P2P distribution, the publishing node simply commits the snapshot locally and peers pull on demand, eliminating the upload wait from the critical path.

Meanwhile, in a typical cluster the nodes that already fetched a snapshot are idle from a network perspective. They could serve artifacts to peers, turning every node into a cache and distribution point.

Goals:

Enable efficient checkpointing by removing the need to upload snapshot artifacts to a central store before the snapshot call returns. Publish locally, distribute lazily to peers.
Better utilize the network by letting nodes fetch template artifacts from the nearest/fastest peer rather than funneling all traffic through a central store.

Originally created by @yingdi-shan on GitHub (Jul 27, 2026). Original GitHub issue: https://github.com/kvcache-ai/AgentENV/issues/12 Originally assigned to: @LSX-s-Software on GitHub. ## Motivation A key driver for P2P distribution is **efficient snapshotting (checkpoint)**. With centralized storage, the snapshot publish path must upload potentially large artifacts (memory + disk checkpoints) to the remote store before the operation is considered complete. This upload latency blocks the snapshot call and limits how fast checkpoints can be taken. With P2P distribution, the publishing node simply commits the snapshot locally and peers pull on demand, eliminating the upload wait from the critical path. Meanwhile, in a typical cluster the nodes that already fetched a snapshot are idle from a network perspective. They could serve artifacts to peers, turning every node into a cache and distribution point. **Goals:** 1. **Enable efficient checkpointing** by removing the need to upload snapshot artifacts to a central store before the snapshot call returns. Publish locally, distribute lazily to peers. 2. **Better utilize the network** by letting nodes fetch template artifacts from the nearest/fastest peer rather than funneling all traffic through a central store.

bsakaguchi added the

enhancement

label

2026-10-29 14:18:18 +00:00

bsakaguchi referenced this issue

2026-10-29 14:20:36 +00:00

[PR #87] [MERGED] feat: support PVM-backed deployment #170