Hello, I use DNN 06.02.03 and the storage company complain about high CPU usage. I did as you recommend in the articlehttp://www.iowacomputergurus.com/comp... : 1. I use Heavy cache. 2. I use hosted jquery version. 3. I enable composite files ( with minify CSS and Minify JS ) 4. I Use Schedule Mode Timer – only for Messaging dispatch every 30 minutes. I also check the eventViewer and the log files for errors and handle them all and now I only have one error repeat every couple of hours ( the last time it occurred was 8 hours ago ) . I also used windbg tool for my website and saw there is problem with function Image.FromFile()And use another code to prevent the problem – and now I don't see errors with this tool. i also use ANTS Performance profiler and i saw that FiftyOne.Foundation.Mobile.Detecation took 28% of the page load time - do i have to use it with the current DNN, or there is a way to disable it ? And still the storage company complains about 37% CPU Usage and 330MB RAM USe when starting the application ( i get event "application start" at the event viewer at the excat time they complain about high cpu usage ). i don't know what to do. do you have any suggestions ? Thank you, Adi damty

hello sebastian,

the Two DB's size is 163MB and 28MB and the recovery model is simple.

what about the FiftyOne.Foundation.Mobile.Detecation that took 28% of the time when the page is load - can i disable it ? or i must use it in this DNN version ?

i also download clean install of DNN 06.02.04 and install it and i use tool performance profiler, and when i start the profile, i look in the task manager and saw the IIS Process go up to 80% CPU Usage during the application start. is that normal ? 

thank you,

adi damty

When an asp.net application first starts up it needs to do a lot of work getting the environment running - which includes compiling code and loading data to the local cache - this will put a high load on any server as it tries to get all this completed as quickly as possibly - you dont want the site to take a week to load. But it should only be for 10-15 seconds.

So if the high usage is only an issue when your app is starting then the easiest option would be to look at running a keep alive service that ensures your app is always up and functional - that way it does not need to go thru the restart and recompile / reload process.

http://www.dnnmonitor.com/ offers a free service that will ping your site on a regular basis and keep the application alive.

Oh as an aside - make sure that your hosting provider is not doing something stupid like automatically closing the asp.net app if it uses too many resources during startup ... this can result in a situation where your app compiles,loads data and launches - does all that hard work - then gets force closed by your host - only to need to start all over again - creating a cycle of heavy cpu usage that is not needed if the app was just left to run and become stable.

But honestly - why do people persist with using hosting companies that simply are not suitable for DNN - there are any number of good dnn hosting companies out there that just work.

Westa