Recently we've been noticing that a lot of our Umbraco-powered websites are running at a very high memory usage, sometimes up to 1.5 GB (!). We've been digging around to see what the problem is, and we found that there is a setting in UmbracoSettings.config that is called "UmbracoLibraryCacheDuration". According to the documentation this is a setting that controls how long the media items and the Members are stored in memory.
This is, by default, set to 1800 seconds, or 30 minutes.
We've played around with this setting and got it down to 10 seconds without finding any performance impact. The memory footprint of the website dropped drastically, from 1 GB tot 300MB. Why is it by default set to 1800 seconds?
I know it's possible to limit the memory usage in the app pool settings, but this seems to be giving me unsatisfactory results.
When you limit the memory, the app pool is recycled everytime more memory is used than the maximum.
The next request, however, is very slow because the app pool has to restart. This becomes a real problem with websites that have a lot of media items (>= 1000), like one of ours as the memory threshold (200MB) is quickly reached and the app pool recycled.
Why is Umbraco using this much memory and can anything be done about it?
UmbracoLibraryCacheDuration: why is it by default 1800 seconds?
Hello everyone.
Recently we've been noticing that a lot of our Umbraco-powered websites are running at a very high memory usage, sometimes up to 1.5 GB (!). We've been digging around to see what the problem is, and we found that there is a setting in UmbracoSettings.config that is called "UmbracoLibraryCacheDuration". According to the documentation this is a setting that controls how long the media items and the Members are stored in memory.
This is, by default, set to 1800 seconds, or 30 minutes.
We've played around with this setting and got it down to 10 seconds without finding any performance impact. The memory footprint of the website dropped drastically, from 1 GB tot 300MB. Why is it by default set to 1800 seconds?
Is there a reason?
First! Thank you! This configuration save my life!
Now I came to retribute... My solution is to use https://www.cloudflare.com/ to reduce the server access!
is working on a reply...