Edit: I ask because AWS suggests a key naming convention for large object amounts to ensure that you're distributing your objects across storage nodes, to prevent bottlenecks.
https://docs.aws.amazon.com/AmazonS3/latest/dev/request-rate...
https://aws.amazon.com/about-aws/whats-new/2018/07/amazon-s3...
Edit Response: I've always used the partitioning conventions they suggest so not sure what sort of impact you encounter without.
I have billions of files. What do?
e.g. if you write 1 million 10KB files per day to S3, you're looking at $150/mo in PUT costs. If you instead write 1,000 10MB blocks, you're looking at $0.15/mo in PUT costs.
Due to S3's support of HTTP range requests, we can still request individual files without an intermediate layer (though our write layer did slightly increase in complexity) and our GET (and storage) costs are identical.
Also just a word of warning, if you do have a lot of files, and you're thinking "let's transition them to glacier", don't do it. The transfer cost from S3->Glacier is absolutely insane ($0.05 per 1,000 objects). I managed to generate $11k worth of charges doing a "small" test of 218M files and a lifecycle policy. Only use glacier for large individual files.
[1] https://docs.aws.amazon.com/AmazonS3/latest/user-guide/creat...