3 ms·
> The git repo is massive so giving each process its own copy is not practical. Just to make sure: This is per point-in-time, and not just because of history?
by yjftsjthsd-h 7y ago
> The git repo is massive so giving each process its own copy is not practical.
Just to make sure: This is per point-in-time, and not just because of history? You can usually make things somewhat cheaper just by doing a shallow clone. But of course that doesn't help if at any given point-in-time the repo is still too big.
- nwellinghoff 7y agocorrect its per point in time. Either way the overlays are a TON faster. :)
- namibj 7y agoEven then, you can actually use multiple external worktrees, saving on the .git folder (or at least any significant size contributions of it).
- the8472 7y agoI don't think git uses copy_file_range yet (at least I can't find it looking through its source), so it'll make expensive copies for each worktree. And he said even deleting the diffs in an overlay is too expensive, which normally should be cheaper than deleting a worktree.