I recently successfully installed DotNetNuke 4.0 via the Control Panel Installer of my hosting company (CrystalTech). I then uploaded one 3rd party module (Enterprise Forms v3.0). The website is on a shared server.

The webserver had previoulsy exising content on it (approx 1200 static HTML pages, and a Snitz forum running off a 30MB Access database). When I installed DNN I did so to test it on my website - I did not remove the previously existing content from the server and vistors to the site are still served the 'old' content (static HTML and Snitz forum). They do not see DNN.

However yesterday I recived an email from my hosting company saying that my site was hogging CPU resources:
"We have determined that your site is responsible for CPU abuse on one of our shared servers. This site was using high CPU levels and causing all sites on that server to resolve slowly or not at all. Because the site was causing the server to become unresponsive, we were not able to determine if a script was causing the issue. So, we have disabled the entire site to protect the performance of the server."

I know there has been no surge in traffic on the site so I am assuming this is related to the DNN install. I have persuaded Crystaltech to reactivate the site for the moment and they are monitoring the CPU consumption. However can anyone identify what the issue may have been an advise what steps I should take to ensure this does not happen again? I provide below an example of a section of the logs captured during the event which may be helpful is assessing the situation.

Thanks

Eoghano

Excerpt from log follows:

Thu 8/3/2006 8:33:51AM [5236] "w3wp" pool identified as Suspect2
Thu 8/3/2006 8:34:23AM [5236] "w3wp" raised to 120 MB in Physical Memory.
Thu 8/3/2006 8:34:23AM [5236] "w3wp" raised to 120 MB in Physical Memory.
Thu 8/3/2006 8:35:49AM [5236] "w3wp" raised to 121 MB in Physical Memory.
Thu 8/3/2006 8:35:49AM [5236] "w3wp" raised to 121 MB in Physical Memory.
Thu 8/3/2006 8:36:31AM [5208] "w3wp" pool identified as Suspect2
Thu 8/3/2006 8:36:31AM [5208] "w3wp" pool identified as Suspect2
Thu 8/3/2006 8:36:31AM [5208] "w3wp" Suspect2, is owned by "NT AUTHORITY\NETWORK SERVICE"
Thu 8/3/2006 8:36:31AM [5208] "w3wp" Suspect2, is owned by "NT AUTHORITY\NETWORK SERVICE"
Thu 8/3/2006 8:36:48AM [5236] "w3wp" raised to 123 MB in Physical Memory.
Thu 8/3/2006 8:36:48AM [5236] "w3wp" raised to 123 MB in Physical Memory.
Thu 8/3/2006 8:36:50AM [5236] "w3wp" raised to 128 MB in Physical Memory.
Thu 8/3/2006 8:36:50AM [5236] "w3wp" raised to 129 MB in Physical Memory.
Thu 8/3/2006 8:36:51AM [5236] "w3wp" raised to 132 MB in Physical Memory.
Thu 8/3/2006 8:36:51AM [5208] "w3wp" CPU usage is 36.44
Thu 8/3/2006 8:36:51AM [5236] "w3wp" raised to 132 MB in Physical Memory.
Thu 8/3/2006 8:36:51AM [5208] "w3wp" CPU usage is 35.84
Thu 8/3/2006 8:36:52AM [5208] "w3wp" CPU usage is 36.42
Thu 8/3/2006 8:36:52AM [5208] "w3wp" CPU usage is 35.47
Thu 8/3/2006 8:36:54AM [5236] "w3wp" CPU usage is 35.40
Thu 8/3/2006 8:36:54AM [5236] "w3wp" CPU usage is 34.70
Thu 8/3/2006 8:36:55AM [5236] "w3wp" CPU usage is 59.24
Thu 8/3/2006 8:36:55AM [5236] "w3wp" CPU usage is 58.92
Thu 8/3/2006 8:36:56AM [5236] "w3wp" CPU usage is 48.36
Thu 8/3/2006 8:36:56AM [5236] "w3wp" CPU usage is 47.02
Thu 8/3/2006 8:36:57AM [5236] "w3wp" HIGH CPU period started.
Thu 8/3/2006 8:36:57AM [5236] "w3wp" HIGH CPU period started.
Thu 8/3/2006 8:37:00AM [5236] "w3wp" HIGH CPU period over, 47.89 avg CPU, using 133926912 Mem,

138842112 PeakMem, 6s elapsed.
Thu 8/3/2006 8:37:00AM [5236] "w3wp" HIGH CPU period over, 48.09 avg CPU, using 133926912 Mem,

138842112 PeakMem, 6s elapsed.
Thu 8/3/2006 8:37:03AM [5236] "w3wp" ended, Suspect2, "NT AUTHORITY\NETWORK SERVICE", 138842112

PeakMem, 1897s runtime.
Thu 8/3/2006 8:37:03AM [5236] "w3wp" ended, Suspect2, "NT AUTHORITY\NETWORK SERVICE", 138842112

PeakMem, 1899s runtime

I'm having the same issue except with v3.3.4.  Everything had been working great for months, then yesterday I did three things: 

1)  I added a "price" to a portal.  Since this is just a property, I wouldn't expect this to be problem unless DNN triggers something off of that price.

2)  I added a first entry to the blog module that I had added to the site the night before.

3)  I created a new portal based on the Club or Organization template.  This is the first new portal I've added since about v3.2.2.  Since this is the most drastic of the three things I did, I'm guessing this is where the problem lies.  Perhaps one of the last upgrades I performed didn't quite do what it should have.

My web host is currently in the process of restoring my sites from tape to where they were two days ago... :(  If this doesn't fix the problem, then I'm truly at a loss.

Ian