Does Google Cloud Storage suffer from sequential naming like Amazon S3?

Question

Amazon S3 suffers a performance penalty if you name your files in a sequential manner (e.g. if your files are "server-.log"). Details here: https://stackoverflow.com/questions/tagged/google-cloud-storage

Does this apply to Google Cloud Storage as well?

Answer 1

From the Naming section of the Best Practices Guide:

Avoid using sequential filenames such as timestamp-based filenames if you are uploading many files in parallel. Because files with sequential names are stored consecutively, they are likely to hit the same backend server, meaning that throughput will be constrained. In order to achieve optimal throughput, you can add the hash of the sequence number as part of the filename to make it non-sequential.