3 ms·
> This seemed odd to me, surely using a cached response would always be faster than making the whole request again! Well it turns out that in some cases, the ne
by sattoshi 4y ago
> This seemed odd to me, surely using a cached response would always be faster than making the whole request again! Well it turns out that in some cases, the network is faster than the cache.
Did I miss a follow up on this, or did it remain unanswered as to what the benefit of racing against the network is?
The post basically says that sometimes the cache is slower because of throttling or bugs, but mostly bugs.
Why is Firefox sending an extra request instead of figuring out what is slowing down the cache? It seems like an overly expensive mitigation…
- 8n4vidtmkvmk 4y agoonly reason i can think of is slow mechanical hard drive vs fast network. or if its based on etag and it has to hash the local resource, but it would be smart to cache that hash too. or maybe the os has too many file handles open and its doing a poor job of reading many files at once, whereas the network offers a 2nd tube to funnel data through...