The first snapshot of a large game shows no progress for its last third #67
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#67
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?
Found on a real install (Cyberpunk 2077, 85 GiB, 5,068 files,
.tools/reviews/dogfood-cyberpunk.md). Sampled every 3 seconds over a 14-minute first snapshot: bytes moved steadily for 8.5 minutes with no file count or file name; then bytes froze at 99% while the file count ran from 599 to 4,996 in about 35 seconds; then nothing changed for about 5 minutes (4,996 of 5,068 files, one file name) until it finished. A player watching the last five minutes sees a stuck bar.Find what the capture is doing in that last stretch (for example the index write, hashing the remaining files, or the commit) and report it as progress, so the display keeps moving or says what step it is on. The file count and name should also move during the byte phase if git reports them. Done when a large first snapshot never shows the same progress for more than a few seconds while work continues, checked against a real large install.