2 ms·
I don't know the details behind CloudFront, so this is just speculation, but based on the assumption that CloudFront pricing is based on the usual AWS "cost plu
by cperciva 15y ago
I don't know the details behind CloudFront, so this is just speculation, but based on the assumption that CloudFront pricing is based on the usual AWS "cost plus" computations, the per-request price looks like it's mostly covering the cost of random disk seeks. For arbitrary request streams, this is a conservative cost model and makes sense; but portsnap bits happen to be cheaper to serve up since most of the requests are for very small patch files which should never be evicted from RAM.
So I don't think Amazon is doing anything wrong with their pricing, nor is this due to HTTP/1.1; it's just that the portsnap bits are "easy" to serve up in ways which are too subtle to be captured by any reasonable CDN pricing model.