Make fewer git process starts per engine operation #262
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 milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
ethan-hann/SavePoint#262
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?
The 2026-10-27 test speed analysis timed every git call in the slowest Core test classes: 17 to 158 git calls per test case, with a median of about 45 ms each, close to the cost of starting git with no work (39-49 ms). Process starts are roughly 50-60% of those classes' time, and every git start also costs players on slow machines (D70). Find the engine operations that start git most often (status, capture, switch, preview) and batch or merge calls (for example one
git status --porcelain=v2instead of several reads,--batchmodes, reusing an index read), test-first, measuring the time of a capture and a switch on a large seeded folder before and after. About 2 CI minutes per 10% fewer calls.Shipped in SavePoint 0.9.22 (PR #274). A capture now starts fewer git processes (first 8 to 5, later 5 to 4, watched 7 to 5, the estimate before the first capture 1 to 0). The switch, check switch, status and preview candidates, and a median-of-several timing, moved to #273.