3 ms·

Then subsequent requests that hit the cache shouldn’t be charged by that logic.

• slt2021 2y ago
  s3 is a complex system, you could be hitting a different node with subsequent requests where this cache entry does not exist yet. if you think egress is expensive, well storing data in RAM for cache purposes is 1000000x more expensive a lot of stuff could be happening. Main problem is AWS (i think) is charging for egress out of S3 system, but customers are looking at their ingress at client side and there is mismatch
  • jpambrun 2y ago
    But you are not charged if it's not Internet egress, which makes your argument about compute/ram cost moot.