3 ms·
> But, isn't subsetting going to result in users now caching your subset instead of a cached copy of everything? Disk is cheap. Particularly disks that you don
by koolba 10y ago
> But, isn't subsetting going to result in users now caching your subset instead of a cached copy of everything?
Disk is cheap. Particularly disks that you don't pay for like your users' disks.
- matt_kantor 10y agoIt's not about disk, it's about network I/O. Making your resource "more unique" means more cache misses and more requests that need to be served (in theory anyway, see Klathmon's sibling comment[0] for more on this). [0]: https://news.ycombinator.com/item?id=13138826 https://news.ycombinator.com/item?id=13138826
- koolba 10y agoNot being a fan of used shared CDNs for static resources[1], I don't see the issue here. They're going to have to download something anyway so from the perspective of your users it's still one download, just smaller. With proper unique namespacing (unique URL per version) and HTTP Cache-Control headers, they only have to download it once (assuming they don't clear their local cache). [1]: Combination of security reasons and unnecessarily coupling apps to the public internet.