I actually have a third module... the FCKEditor.  Have a feeling that's not the culprit.  Sounds like I will not want to go to 4.3 at this time.

I have deleted the dll with Smart Thinker.  Do I need to reset IIS or anything before testing?

ok... i removed the dlls for the two modules.  I seem to be able to get to the site now, but the cpu usage is still through the roof and the site takes well over a minute to load (but at least it doesn't time out now).  i can log in successfully, but everythin is taking a very long time to work.

Someone posted a whole list of ways to tune DNN to perform better, but I cannot find it. One of the things is to turn off any schedules you don't need, look at their logs to see how long they run and if any time out. I find file synch timing out on a lot of portals -- but this is sorta needed...

If you can live without site logs and error logs, turn those off.

If you have access, put each portal install and other .net web apps in their own app pool. Adjust the recycling, performance, and health to prevent the apps from crashing or overloading the server.

If you really want to get into it, and you have remote access, use SQL Profiler to temporarily track all the calls to the database from your DNN. It takes some times to set-up, but you can see yourself browsing the website and on profiler exactly which stored procedures are hanging up your website.

---

Jason Honingford - Web & Software Developer
www.PortVista.com