To be honest, I personally don’t find it weird that is needs 500MB of RAM or more. It’s a content management system with a lot of background tasks, services etc.
Well I get that but still … Umbraco can be used in so many ways. I would think that a specific Umbraco solution have very different needs from another. The need for caching media, content internal / external, content delivery api must vary by a lot. And while some solutions might benefit from caching all on startup and keeping it in mem, others might not (specially if the caching is done elsewhere - in frontend for instance.
Since we use Umbraco Headless and with media served via external services - its pointless for us to have Umbraco wired up to serve from cache.
Umbraco introduces HybridCache which has some options I need to learn. But it would be amazing to know if there are any knowledge in this area hidden in docs or brains
Are you aware of the new caching settings with hybridcache? You can change the duration / max size of the cache and can also change which things are seeded in the cache on startup: Cache Settings | Umbraco CMS
I think you can attribute most of this to the architecture and framework it’s built on. I don’t know of many .NET applications that don’t immediately balloon up to large memory footprints like this.
I’ll be watching this topic closely–I’d love to hear more and possibly follow along to get our applications memory footprint down too.