Does Google Cloud Storage need to optimize a key prefix for speed like AWS S3?

Question

AWS S3 recommends optimizing the key prefix to avoid hot spots,

eg. http://docs.aws.amazon.com/AmazonS3/latest/dev/request-rate-perf-considerations.html

Is this also required or recommended for Google Cloud Storage?

Answer 1

As mentioned in this previous answer :

splitting objects into more "subdirectories" does not make any scalability or performance difference

More specifically, the name of an object does not affect the performance or scalability of accessing objects in the bucket.