Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Performance and...Performance and...Memory optimisationMemory optimisation
Previous
 
Next
New Post
10/21/2013 12:55 PM
 
Hello,
memory may not be that expensive any more, but the average memory required to run a static site with low traffic has increased tremendously since version 4, touching peaks of 300MB and more on dnn7. Of course, we have lots of more features and all the rest of it. However, there should be a way to reduce the memory footprint by disabling something.

The first thing that comes to mind (there might be others) is the social bit, or " glorified intranet". Can one disable that (how?) and possibly save memory? What else can be done? Is there a document describing what memory is used by what function/module/feature?

Any input appreciated

Franco
 
New Post
10/23/2013 11:28 AM
 
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 C# MVP, MCITP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

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
 
New Post
10/23/2013 6:44 PM
 
If you need to care about the memory footprint, I doubt that DNN is the proper solution for you, sorry.
You might decrease object caching and move output caching to files, but will still end up with a serious amount of memory required.

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/24/2013 4:32 AM
 
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
 
New Post
10/25/2013 4:20 AM
 
Franco,
I agree.
But if you check the code, you will notice a lot of room for optimization. I am sometimes under the impression that design focuses more on clean code and implementation of patterns than memory requirements and CPU utilization. If you take User management for example, to display 20 users up to 81 database calls are performed and complete data of every user listed gets loaded and cached. Simple search in Member Directory module times out on sites with many users, because from 2nd or 3rd character being typed, all matching users are loaded with membership and profile data.
Many evaluations are done on API level instead of the database, which also decreases performance.

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Performance and...Performance and...Memory optimisationMemory optimisation


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.

Content Layout

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out