I have been trying to track down some performance issues with my DNN 7.4.2 installation on Azure Websites.  I noticed when either a new user or current user account is accessed via the /User-Accounts/ page that the popup dialog takes a very long time to come up and display the user account.  So I went to the website monitoring and saw the response time went over 30 seconds and sometimes longer.  So next I checked the SQL Azure database monitoring and noticed it pegged at 100% of the DTUs (using the Basic with 5 DTUs) which is also 100% CPU. 

So I set up a performance report and profiler in my local lab to try and replicate the issue.  In the lab I only saw 50 to 60% CPU utilization.  I am using SQL 2014 Standard in my lab.  Azure is using v12 version.

Any ideas on why this is happening? Or suggestions on how I can mitigate or pinpoint the issue?  One day this week, the entire site froze while there was high traffic and while I was trying to authorize a new user.  SQL had pegged at 100% several times and response times went over 3 to 4 minutes.  I think that was possibly a perfect storm of having the scheduler in timer mode along with the user account issue combined with high traffic. 

I have gone through all of the various suggestions on how to improve performance.  I am using a CDN for my high traffic media items. I have trimmed down the scheduler and put the site search at 1 day and set it for off peak times. 

But this one thing with accessing and editing user accounts, I have not found any suggestions in posts here or elsewhere.  Any ideas or help would be greatly appreciated.  Thanks!

Sebastian,

Thank you for taking the time to respond.  I did some more checking and it looks like right after an AppPool restart it pegs the SQL Server CPU at 100%, but drops down quickly.  Subsequent lookups to the same user or other users only spike at 20 to 30%.  I guess I will just make sure I do not approve new users during a peak time right after a restart.  :)

This has probably been going on for a long time, but now on Azure I am able to see the impact dynamically with the monitoring tools.  Thank you for the efforts on the Turbo scripts. I have downloaded them and will check them out. 

I am onto trying to filter out the 404 errors, spam attacks and robot calls.  Version 7.4.2 is way better at handling those events than the 5.6.8 that I was on.  It has been a long journey since the original IBuySpy on ASP.NET. Where has the time gone!!  :)

Wow, that's a lot of processing in the background.  I'm new to DNN and setting up a new instance.  I would like for DNN to handle my security and authentication for the website including both CMS users and website members.  Your comments have me a little concerned about performance.  I have 3 possible ways to go and am looking for some recommendations. 

•  I have a content management staff of about 100 users. 
•  I have about 35,000 active website user personal accounts (requires the addition of several fields to the standard DNN profile).  
• I have about 900,000+ website members overall (requires the addition of even more  fields to the standard DNN profile).

I can handle the login/authentication/storage of user info outside of DNN if I must or try a hybrid state where only auth is handled by DNN and all user info is stored outside DNN's main framework.  I just hate to have duplicated info in multiple places to look up to handle all my users authentication, preferences, maintenance, and storage.  Based on these processing architectural challenges, which level of DNN user setup would you recommend for handling my scenario?