You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some time in the future, I think GitButler will keep creating Git trees from the worktree contents. And I say that because I am not going to challenge it until everything works perfectly with the current system, and is tested perfectly as well.
With that in mind, one will either have to exclude big files, or… learn how to handle them quickly.
And there I think gitoxide can can provide a knob to turn and basically turn off compression when writing loose objects. This would allow data to be read and written as is, with performance approaching whatever maxes out the disk for reads and writes. In numbers, I'd think that a moderately fast CPU core can compress with 25MB/s, but write 1000MB/s easily on even somewhat slow SSDs. This should bring the time to add a such a file to a tree down from 2s (which probably has something to do with the slowdown) to something closer to 50ms, a 40x improvement.
Could it really be that straightforward? I surely hope this plays a big part in it.
eg .iap or .zip 30-50mb in size
Reported on discord
https://discord.com/channels/1060193121130000425/1073202153163857920/1295404335777320960
The text was updated successfully, but these errors were encountered: