Decide pack.compression for large files #45
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
ethan-hann/SavePoint#45
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A reproduction of a first snapshot with three 1.5 GiB files (random data) measured about 50 MB/s, and most of the time is zlib on the streamed pack: files above core.bigFileThreshold (128m) stream into objects/pack/tmp_pack_*, and core.looseCompression=0 does not cover them; pack.compression does. Setting pack.compression=0 would likely speed large first snapshots a lot (an earlier measurement found looseCompression=0 gave 2.2x on capture) and make the byte progress near exact, at the cost of disk space for large files that do compress (game archives are usually already compressed, uncompressed textures and audio are not). Measure capture time and store size on a real large game (for example a 70 GB install) with and without it, then decide, and record the call in docs/decisions.md.