Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
We recently deployed a website which was about 15GB in total with quite a few images using Umbraco 7.1.8
Everything was fine until we got a notification from Microsoft telling us we are using 180% of the allocated space, i.e. the site was up to 90GB.
Further investigation revealed it was the App_Data/cache folder being more than 50GB in size.
We recently deployed a similar site in size and type (basically sites for large theme parks) and no problems here (also 7.1.8).
We are using http://imageresizing.net/ for our image resizing so we really don't need this caching from Umbraco, especially at these sizes.
When trying to delete the files it give errors saying that some of the files are in use. We have created a scheduled task to try and delete all the files this cache folder creates to ensure the site does not go over the size limit enforced by Azure.
Any ideas why this folder is so big? Or how to disable it?
Sounds like the ImageProcessor cache folder.
Is there any way to disable it?
The http://imageresizing.net cache folder is in the root of the site and it's a moderate 2GB if finle size, which is what we would expect.
It seems there are two possible solutions: http://our.umbraco.org/projects/collaboration/imageprocessor/feedback-for-imageprocessor/47626-Is-there-an-onoff-switch
I don't see that ImageProcessor config file in my installation, so not sure if that's something to be expected in all installations.
Did both of those and the cache folder is still growing.
You can delete the cache folder and let ImageProcessor start over again?
Maybe there were a lot of "dead" images?
I don't think deactiving caching of ImageProcessor is the solution as it would mean generating your modified images on the fly all the time.
Also, ImageProcessor would not be generating files in the cache folder if it were not being used. Are you sure you are using ImageResizer? Assuming you are, I would recommend you remove the ImageProcessor HTTP handler from web.config.
Removed the HTTP handler and stopped the website. Deleted the cache folder and started the service up again.
Looks like it's behaving now (without the image processor). It removed approx 50GB of images for a site that's only 10GB in total, so some form of cache clearance strategy is probably needed. We are definitely using image resizer which currently has about 2 GB worth of images in cache and cleans the image out if not used within a certain duration.
Thanks for the help
Just curious, is this a common issue with ImageProcessor or can it be prevented simply by decreasing the maxDays in the cache.config?
Faced the same issue. Cache size was 12 GB after image changes in 2 days. Stopped the site. Cleared cache and restarted. Will observe.
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted