3 ms·
Is this a problem in Go itself? Isn’t this something the Git-lfs should be changing in only lfs? It seems reasonable to prefer a short delay by default, but wh
by Aeolun 4y ago
Is this a problem in Go itself? Isn’t this something the Git-lfs should be changing in only lfs?
It seems reasonable to prefer a short delay by default, but when you are sending multi-magabyte files (lfs’s entire use case) it seems like it would be better to make the connection more reliable (e.g. nobody cares about 200ms extra delay).
- morelisp 4y agogit-lfs authors agree and point out regular git also disables Nagle. https://github.com/git-lfs/git-lfs/issues/5242 https://github.com/git-lfs/git-lfs/issues/5242