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
It seems that git lfs can eat lots of bandwidth without caching, although I don't get why it would need more than without git lfs. Is it just a case that git lfs downloads all files in the pipeline, whereas in a normal pipeline files can be cached more easily -- or is the concern simply that those who use git lfs usually have large files, hence caching becomes important?
If it is worse than the prior solution then (i) why did I start using it and (ii) let's cache it.
The text was updated successfully, but these errors were encountered:
It seems that git lfs can eat lots of bandwidth without caching, although I don't get why it would need more than without git lfs. Is it just a case that git lfs downloads all files in the pipeline, whereas in a normal pipeline files can be cached more easily -- or is the concern simply that those who use git lfs usually have large files, hence caching becomes important?
If it is worse than the prior solution then (i) why did I start using it and (ii) let's cache it.
The text was updated successfully, but these errors were encountered: