10 Comments on “which naming scheme would give optimal performance on S3?”

1. sivaguru says:

   July 20, 2017 at 2:39 am

   B. instanceID_log-HH-DD-MM-YYYY

   
   
   
   2

   
   
   
   5
2. McEphin says:

   August 14, 2017 at 10:35 am

   D

   http://www.aiotestking.com/amazon/which-naming-scheme-would-give-optimal-performance-on-s3/

   
   
   
   2

   
   
   
   0
   1. McEphin says:

      August 14, 2017 at 10:36 am

      I am sorry, D is not correct on this question

      Sivaguru is correct, B instanceID_log-HH-DD-MM-YYYY

      
      
      
      1

      
      
      
      1
      1. Sadeel Anjum says:

         September 9, 2017 at 1:55 pm

         C is correct
         Ref URL :
         http://docs.aws.amazon.com/AmazonS3/latest/dev/request-rate-perf-considerations.html

         
         
         
         0

         
         
         
         1
         1. TuanBA says:

            October 10, 2017 at 4:14 am

            C is answer

            
            
            
            0

            
            
            
            1
3. Sadeel Anjum says:

   September 9, 2017 at 1:53 pm

   C. instanceID_log-YYYY-MM-DD-HH

   
   
   
   0

   
   
   
   1
   1. Sadeel Anjum says:

      September 9, 2017 at 1:54 pm

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

      
      
      
      0

      
      
      
      1
4. AWS Enthusiast says:

   December 13, 2017 at 11:47 am

   D

   If an application is storing hourly log files from thousands of instances from a high traffic web site, which naming scheme would give optimal performance on S3?
   Sequential
   instanceID_log-HH-DD-MM-YYYY
   instanceID_log-YYYY-MM-DD-HH
   HH-DD-MM-YYYY-log_instanceID (HH will give some randomness to start with instead of instaneId where the first characters would be i-)
   YYYY-MM-DD-HH-log_instanceID

   http://jayendrapatil.com/aws-s3-best-practices/

   
   
   
   2

   
   
   
   0
5. Vergnac Cyril says:

   December 20, 2017 at 5:53 am

   The good answer is the most random prefix

   Each hour, all parameters are equals except instanceID because there are thousands of instances
   So, it’s B or C
   Not D because HH is the same for all instances at a given moment.

   The mentionned URL is good:
   http://docs.aws.amazon.com/AmazonS3/latest/dev/request-rate-perf-considerations.html
   You can read:
   If you anticipate that your workload will consistently exceed 100 requests per second, you should avoid sequential key names. If you must use sequential numbers or date and time patterns in key names, add a random prefix to the key name. The randomness of the prefix more evenly distributes key names across multiple index partitions.

   After that, i choose B because the next hour, the only change is the hour HH
   So it’s more random than YYYY

   
   
   
   0

   
   
   
   1
6. webber says:

   January 25, 2018 at 2:58 am

   C

   
   
   
   0

   
   
   
   1