This has been enabled on GitLab.com for over a week. There were hundreds
of thousands of /internal/lfs of API calls made from the new Gitaly
LFS smudge filter with no apparent errors. Project archives are cached
via a CDN on GitLab.com, and for self-managed hosts Workhorse also has a
local disk cache, so that mitigates any extra network traffic generated
by larger archives.
https://log.gprd.gitlab.net/goto/97ba3b8c821c13c97929532bdcee1920 shows:
There were a few thousand 404 errors, but a spot check shows those LFS pointers did not exist as entries in LfsObject.
Relates to #268409 (closed)