I have some questions:
What are advantages of using Git LFS over simple Git for storing large files in repo?
What is the maximum size of file that Git LFS can store upto?
What are the cons of using Git LFS?
CodePudding user response：
Git Large File Storage (LFS) is a Git extension that improves the handling of large files in Git repositories. It allows you to store large files such as audio, video, and graphics, directly in your Git repository, while keeping the history of your repository small and efficient.
Here are some of the advantages of using Git LFS over simple Git for storing large files in a repository:
Git LFS stores large files in a separate storage system, rather than in the Git repository itself. This means that your Git repository remains small and efficient, even when storing large files.
Git LFS tracks only the metadata of large files, such as their size and content hash, in the Git repository. This allows you to easily manage and track changes to large files, without having to store the entire file in the Git repository.
Git LFS automatically downloads and caches the large files you need, as you need them. This means that you only have to download the large files that you actually use, rather than the entire repository, making it faster and more efficient to work with large files in Git.
Git LFS integrates seamlessly with Git, so you can use it with your existing Git workflow and tools. This means that you can use Git LFS without having to learn new commands or change your existing processes.
While Git LFS has many advantages, there are also a few potential disadvantages to consider:
Git LFS requires additional setup and configuration to use. This means that you will need to install and configure Git LFS on your local machine and Git host, as well as on any other machines that will be used to access your repository.
Git LFS uses a separate storage system to store large files, which can add complexity to your Git workflow. This means that you will need to manage both your Git repository and the Git LFS storage system, and ensure that they are properly integrated and synchronized.
Git LFS can have performance and scalability implications, depending on how you use it. For example, if you store large files in a single branch or commit, it can make that branch or commit difficult to clone or checkout, and can impact the overall performance of your Git repository.
Git LFS requires a Git host that supports it. Not all Git hosts support Git LFS, so you may need to switch to a different Git host or pay for additional Git LFS storage in order to use it.
Overall, using Git LFS can make it easier and more efficient to manage and work with large files in a Git repository. If you are dealing with large files in your Git repository, using Git LFS is definitely worth considering.
There is no maximum file size limit for Git LFS. Git LFS can store any file size that is supported by your Git host, storage provider, and network infrastructure.