Skip to content

upload: interleave packing and uploading to bound staging disk #72

Description

@SgtPooki

Description

upload runs plan, then packs the entire CID list into CAR files, then starts uploading. Peak staging disk is therefore roughly the total size of the migration, even though CARs are evicted as copies commit during the upload phase.

Impact

The runbook has to tell users to budget free disk equal to their data size. Issue #70 set out to keep the disk footprint near the pack target ("upload each ASAP, to keep disk small"), and #69 (hosted aggregator) assumes the local flow is disk-light for most users.

Proposed next step

Interleave: build one bin, hand it to the upload loop, build the next while the upload streams. The commit batcher already tolerates pieces arriving over time, so only the pack scheduling moves.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    Status
    📌 Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions