Comment by nightpool
3 years ago
Certainly you'd agree that this is a bug in git lfs though, correct? And users doing "git push" with their 500MB files shouldn't have to think about tinygrams or delayed ack?
It's reasonable to think about what other programs might have been affected by this default choice (I'm sure I used one myself two weeks ago—a Dropbox API client with inexplicably awful throughput) and what a better API design that could have avoided this problems might look like
Maybe golang should default to panicking if the application repeatedly calls send() with tiny amounts of data :)
I don't know enough about git-lfs to say. Things that need buffering should deliberately buffer, I guess?