It seems like the displaying of images is really slow, which makes me think that the images aren't being cached properly and that they are rebuilding each time.
Text-only images that are generated are saved to the /data/cached folder.
For image-related images, they are saved in a 'cached' folder directly beneath the folder that contains the image. For example... if you had an image in the /media/1234 folder, ImageGen would create a /media/1234/cached folder to hold any resized images.
Be sure that you're running the v2.2 patch update as well, as it has an important caching bug fix.
Remember that the umbraco.library:GetMedia() call hits the database, which is therefore slower than calls that just hit the xml content cache. You can make the GetMedia() calls faster by setting the second parameter to 'false' so it doesn't search sub-folders. And, if you have fewer images in a media 'folder' you'll also have faster response from the GetMedia() call because you'll have fewer database requests.
VistaDB is also slower than other databases, which magnifies the issue somewhat. In a production environment I'd use something other than VistaDB to get the performance boost.
What are the chances of being able to specify the cache location in the config file in a future update ? That'd be really useful for locked down sites where write permission is only given to specific folders.
Where do the images cache?
It seems like the displaying of images is really slow, which makes me think that the images aren't being cached properly and that they are rebuilding each time.
Where should I look to see if this is true?
Thanks,.
C
Hi, Chad,
Text-only images that are generated are saved to the /data/cached folder.
For image-related images, they are saved in a 'cached' folder directly beneath the folder that contains the image. For example... if you had an image in the /media/1234 folder, ImageGen would create a /media/1234/cached folder to hold any resized images.
Be sure that you're running the v2.2 patch update as well, as it has an important caching bug fix.
cheers,
doug.
Thanks. They're definitely caching. Must be a slow server and the fact that I'm using VistaDB that is causing the issues.
-C
Yes, that might be it.
Remember that the umbraco.library:GetMedia() call hits the database, which is therefore slower than calls that just hit the xml content cache. You can make the GetMedia() calls faster by setting the second parameter to 'false' so it doesn't search sub-folders. And, if you have fewer images in a media 'folder' you'll also have faster response from the GetMedia() call because you'll have fewer database requests.
VistaDB is also slower than other databases, which magnifies the issue somewhat. In a production environment I'd use something other than VistaDB to get the performance boost.
Another option is to use the cached media package in the umbraco projects section. http://our.umbraco.org/projects/cultiv-mediacache Though I've not used it myself it sounds very promising!
cheers,
doug.
Hi Doug,
What are the chances of being able to specify the cache location in the config file in a future update ? That'd be really useful for locked down sites where write permission is only given to specific folders.
Thanks,
Hendy
is working on a reply...