One of my sites is now experiencing performance problems. Now there are 30-40 connections to the site at a time. Although IIS works perfect with 4 threads, SQL acces is tremendous and SQL eats 100% of the memory given to it. I have 13 DNN sites on that machine (It is a power one with 2 Xeons and 4 Gig RAM) when I stop this particular site CPU goes back to 2%. Only this site gets this much access and others get 3-10 conections at a time.

I first used Moderate RAM caching, then stoped all scheduled modules, then used Heavy caching (both tried RAM and Disk). But nothing changed.

So this shows me that if the site grows more My SQL machine (which is a separate machine than the Web Server) will eat the CPU in a short time.

Does anybody tried DNN under heavy site conditions. I'm using DNN 3.1.1 which is a stable release. I don't use 3.2.2 since it has a bug in Skin (Menu do not Justify. Even if you give a justify it goes to left).

Thanks,
Can

Thanks for the update Can, good to know it wasn't a DNN problem.

Can
Can you let us know some more details on the stored procedure and what you did to fix it, please?
If it was part of the core or a module would be nice to try and get it fixed at the core or at least us other 3.1.1 users can stop a problem before it happens.
TIA
Antony