Git Large File Storage

[Chris King]

at what point should files be considered large ?

and what are the benefits to using LFS ?

[ThiagoBomfim · Accepted solution]

The definition of a large file is up to you, really. Long story short problem with large files on Git is that if they are modified throughout several commits, when devs checkout the code they'd be downloading all of the "large" files that are being tracked by Git. By using LFS, when you checkout a repo that has LFS enabled, devs will checkout a the big file on the latest commit but not all the previous ones unless they change to that commit. Only a small text file containing instructions on how to download the "large file" are stored in previous commits and hence prior versions are checked out on demand (i.e. if they checkout that commit/branch etc).

You can define whatever files you like to be a "large file" and then those will be handled that way bit Git when people clone that repo.

In-depth details: Atlassian Git LFS Tutorial

[Chris King]

Thanks Thiago

Understanding how the files will be treated on the server makes all the difference. 

The size of the file makes little difference,  it is how it is used.

(edited after the fact, due to not being able to see what I was typing via a phone)

[ThiagoBomfim]

That's exactly right. You will have to tell Git LFS which files you want it to track (i.e. specific files, extensions like .psd or .bmp). It is all up to you. I am glad it helped.