Long minimumCacheTTL in next.config
Hey everyone! I'm contemplating the idea of setting a really long minimumCacheTTL for scenarios where images rarely, if ever, change. Imagine a massive website with around 100,000 static images.
Would there be benefits to having a minimumCacheTTL of, say, a year? As far as I grasp, this would keep the optimized image saved on the server's disk (within .next/cache/images) so it wouldn't need re-optimization, saving CPU resources and preventing image loading delays. The obvious trade-off is disk space, but assuming that's not an issue, are there other considerations I might be missing?
0 Replies