3 ms·
In general, whenever you introduce a cache to make software faster (along any dimension), you have to think about cache invalidation and eviction. If your softw
by sunshowers 1y ago
In general, whenever you introduce a cache to make software faster (along any dimension), you have to think about cache invalidation and eviction. If your software is fast enough to not need caching, this problem goes away.
- zahlman 1y agoIt's funny because superior caching is also highly relevant to uv's outperformance. (But invalidation/eviction isn't generally a real problem for a cache of installed packages; the cache can be cleaned up whenever and just rebuilt , and the cache has a separate entry per version of a library, where each version is immutable.)
- sunshowers 1y agoAgreed -- the dream of caching is immutability.