|
Friday 25 March 2011 9:19:03 am
We have a client whose site sits behind an "origin pull" CDN ("origin pull" is where you don't have to upload your assets to the CDN, but where the CDN automatically downloads and stores your assets when pages are requested). We're looking at ways to optimize the CDN setup. One potentially big optimization we've identified is for images and other files stored in var/site_name/storage. All images on the site are currently cached by the CDN for 1 day, which might make more sense for site design images hard-coded into templates and present in stylesheets. However, by my analysis, all files that sit under var/site_name/storage are versioned, with paths such as: var/site_name/storage/images/media/images/matrix_public/1123-1-eng-US/matrix_public.jpg That would mean that all paths under that folder contain unique assets, and that new assets are never uploaded to existing paths. If that's the case, we could cache everything under var/site_name/storage for something like 1 year, or essentially indefinitely. Are there any exceptions under var/site_name/storage? Can we assume that each such URL contains content that is permanently at that URL?
http://www.mugo.ca
Mugo Web, eZ Partner in Vancouver, Canada
|
