If you are worried about the footprint, ensure that all caching modes are set to file. That will reduce the footprint and even on DNN 7.x it should be around 100mb for the worker process. Keep in mind that your third party modules in use are also going to have an impact.

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services

Sebastian,
you may be right, and certainly dnn is not suitable for all uses, but we are in the "performance and optimisation" discussion forum and memory must be part of that, otherwise what's the point? Ruling it out that way does not make any good for the community. Every applicaiton or framework need to worry about the resouce usage to stay in the marketplace. Instead of discarding the question we should look at ways and means to improve that and even push the developers to take into high consideration this aspect. The same is done, I hope, for scripts and sprocs to make them more efficient in terms of CPU: we have seen dnn making usage of hosted jquery, telerik, etc. One of the reasons for that is speed.

There are certainly reasons for such and heavy memory usage, and caching is among those, but there should be ways to configure that and avoid using/wasting memory when not needed. I am in favour of lean approaches, not dinosaurs :-)

Franco