You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 6988cb0
Browse filesBrowse the repository at this point in the historyBrowse files
fix(snapshot): revert digest tracking on compaction output paths
5afd9d1 wrapped every compact_to output in DigestTrackingFile +
OrderedWriter so OSS/ACR publish could skip re-hashing sealed layers.
On all snapshot packing paths this:
- forces ordered writes, dropping compaction write concurrency from
32 to 1 on the raw output path (the default for memory snapshots
and the only mode for rootfs lower rewriting), and
- adds synchronous software SHA256 over every written byte on the
capture hot path.
The descriptor it produces is only consumed by the OSS repository
backend, the ACR source-registry publisher, and (opportunistically)
P2P content-addressed layer advertisement; posix_fs and local-only
snapshots pay the cost with zero benefit. Even for OSS the trade is
negative in the standard flow: publish runs in the same synchronous
request as capture with a warm page cache, so the saved re-read costs
nothing, while the serial-write penalty is real. Inherited layers
already carry descriptors from the parent manifest via OSS runtime
resolution, so there is no per-publish re-hash multiplier either.
Revert the descriptor plumbing (compact_layers,
publish_memory_overlaybd_layer, build_mem_snapshot_image_config and
their callers) and remove DigestTrackingFile/OrderedWriter. Keep the
OSS multipart upload parallelization from the same commit (64 MiB
parts x 8 concurrent), which is unrelated and beneficial. Publish
paths without descriptors already fall back to explicit hashing
(import_managed_layer_by_hash / dense export), and P2P falls back to
uuid-keyed layer artifacts.
Fixeskvcache-ai#184.
0 commit comments