git lfs migrate
With our latest release,
git lfs migrate ships with a native implementation for reading packed objects: an important next step to making Git LFS’s migrator performance significantly faster. Git LFS also learned how to avoid saving unchanged objects, making it 52% faster to examine your repository for large objects than in previous releases.
~/g/git-lfs (master) $ git lfs version git-lfs/2.2.1 (GitHub; darwin amd64; go 1.8.3; git 621d1f82) /g/git-lfs (master) $ time git lfs migrate info migrate: Sorting commits: ..., done migrate: Rewriting commits: 100% (5840/5840), done # ... git lfs migrate info 36.30s user 19.80s system 147% cpu 38.127 total
~/g/git-lfs (master) $ git lfs version git-lfs/2.3.0 (GitHub; darwin amd64; go 1.8.3; git 70995b39) ~/g/git-lfs (master) $ time git lfs migrate info migrate: Sorting commits: ..., done migrate: Examining commits: 100% (5840/5840), done # ... git lfs migrate info 23.74s user 5.71s system 162% cpu 18.144 total
git clone command is now 170% faster on repositories using Git LFS than in previous releases. That means the native
git clone command is as fast as the (now deprecated)
git lfs clone wrapper. With simultaneous object batching and transferring, you can expect dramatic performance improvements for tools that shell out to
git clone or
You’ll also find support for new transfer agents, release targets, documentation, and more—all of which are thanks to gracious contributions from the Git LFS open source community.
For more information about the Git LFS v2.3.0 release, check out the release notes.