Comment on S3 as a Git remote and LFS serverComments−zmmmmm1yJust remember, the mininum billing increment for file size is 128KB in real AWS S3. So your Git repo may be a lot more expensive than you would think if you have a giant source tree full of small files.−justin_oaks1yThat 128KB only applies to non-standard S3 storage tiers (glacier, infrequent access, one zone, etc)S3 standard, which is likely what people would use for git storage, doesn't have that minimum file size charge.See the asterisk sections in https://aws.amazon.com/s3/pricing/−zmmmmm1yThank you for highlighting that, I had remembered it wrongly.−afro881yLooks like it uses bundles rather than raw files: https://github.com/awslabs/git-remote-s3?tab=readme-ov-file#...−chrsig1yalso the puts are 5x as expensive as the get operations
Comments
Just remember, the mininum billing increment for file size is 128KB in real AWS S3. So your Git repo may be a lot more expensive than you would think if you have a giant source tree full of small files.
That 128KB only applies to non-standard S3 storage tiers (glacier, infrequent access, one zone, etc)
S3 standard, which is likely what people would use for git storage, doesn't have that minimum file size charge.
See the asterisk sections in https://aws.amazon.com/s3/pricing/
Thank you for highlighting that, I had remembered it wrongly.
Looks like it uses bundles rather than raw files: https://github.com/awslabs/git-remote-s3?tab=readme-ov-file#...
also the puts are 5x as expensive as the get operations