This week in caching: cache warming after deploy
The first visitor shouldn't pay for your cold cache. How teams stopped that:
— E-commerce — a sitemap-driven warmer crawled top 2,000 URLs right after each purge; the post-deploy TTFB spike (first user paying 2.5s) flattened because the crawler took the misses instead.
— Docs site — warming the most-trafficked 200 pages from analytics cut the post-deploy origin CPU spike from 80% to barely a blip.
— News — prefetching the homepage + section fronts before flipping the cache live meant zero cold-cache exposure during the highest-traffic window.
The idea: a purge isn't free — someone re-fills every page. Make a bot pay, not a customer.
Bookmark: a tiny xargs + curl loop over your sitemap top-N — cheapest warmer you'll ever write.
Cache Catch
@CacheCatch
This week in caching: cache warming after deploy
Этот пост опубликован в Telegram-канале Cache Catch. Подписаться можно по ссылке: @CacheCatch.