Regional Cache
An architectural pattern that replicates hot data to edge locations near compute nodes to shorten the read path, similar to how a CDN caches static assets. Its core principle is that the origin storage remains unchanged while reads are served from nearby locations.
Timeline (last 90 days)
The regional cache mechanism caches reused image data closer to where the Sandbox runs, and on a cache hit, initialization reads the nearby local cache data directly instead of going back to the image storage in iad1.
The regional cache covers managed images and custom images supported by the Vercel Container Registry, as well as snapshots created from these images.
The farther a region is from the origin storage, the more pronounced the startup improvement brought by the regional cache; regions close to the origin storage see relatively smaller improvements.
The speedup effect is based on cache hits; on the first pull or a cache miss, the data still needs to go back to the origin, and the startup path is the same as before.
For workloads that frequently reuse the same image, the benefit of the regional cache is most direct; in scenarios where images change frequently, the cache hit rate will be affected.
In the regional cache architecture, the authoritative copy of the image remains in iad1, and the regional cache merely adds a hit-able local copy in front of it, with no changes needed to the write and consistency logic.
The regional cache needs to maintain cache invalidation and hit rates, and first access or cache eviction still requires going back to the origin.
For workloads that rely on image sources other than the Vercel Container Registry, the regional cache optimization does not currently apply.
All Facts (8)
The regional cache mechanism caches reused image data closer to where the Sandbox runs, and on a cache hit, initialization reads the nearby local cache data directly instead of going back to the image storage in iad1.
50%UnverifiedThe regional cache covers managed images and custom images supported by the Vercel Container Registry, as well as snapshots created from these images.
50%UnverifiedThe farther a region is from the origin storage, the more pronounced the startup improvement brought by the regional cache; regions close to the origin storage see relatively smaller improvements.
50%UnverifiedThe speedup effect is based on cache hits; on the first pull or a cache miss, the data still needs to go back to the origin, and the startup path is the same as before.
50%UnverifiedFor workloads that frequently reuse the same image, the benefit of the regional cache is most direct; in scenarios where images change frequently, the cache hit rate will be affected.
50%UnverifiedIn the regional cache architecture, the authoritative copy of the image remains in iad1, and the regional cache merely adds a hit-able local copy in front of it, with no changes needed to the write and consistency logic.
50%UnverifiedThe regional cache needs to maintain cache invalidation and hit rates, and first access or cache eviction still requires going back to the origin.
50%UnverifiedFor workloads that rely on image sources other than the Vercel Container Registry, the regional cache optimization does not currently apply.
50%