title: S3 partitioning strategy
body: <p>fully aware of the documentations about how to name a S3 object within a bucket to optimize performance</p>
  
  <p>can not understand the example in this article <a href="https://aws.amazon.com/blogs/aws/amazon-s3-performance-tips-tricks-seattle-hiring-event/" rel="nofollow">https://aws.amazon.com/blogs/aws/amazon-s3-performance-tips-tricks-seattle-hiring-event/</a></p>
  
  <pre><code>2134857/gamedata/start.png
  2134857/gamedata/resource.rsrc 
  2134857/gamedata/results.txt
  2134858/gamedata/start.png
  2134858/gamedata/resource.rsrc
  2134858/gamedata/results.txt
  2134859/gamedata/start.png
  2134859/gamedata/resource.rsrc
  2134859/gamedata/results.txt
  </code></pre>
  
  <p>the article says "All these reads and writes will basically always go to the same partitio"</p>
  
  <p>but we should have three partitions</p>
  
  <p>2134857, 2134858, 2134859</p>
  
  <p>, right ?</p>
  
  <p>if we reverse the id</p>
  
  <pre><code>7584312/gamedata/start.png
  7584312/gamedata/resource.rsrc
  7584312/gamedata/results.txt
  8584312/gamedata/start.png
  8584312/gamedata/resource.rsrc
  8584312/gamedata/results.txt
  9584312/gamedata/start.png
  9584312/gamedata/resource.rsrc
  9584312/gamedata/results.txt
  </code></pre>
  
  <p>we have also three partitions 7584312, 8584312, 9584312</p>
  
  <p>what is the difference.</p>
  
  <p>What is the definition of a prefix and its relationship to partitioning strategy.</p>