Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Performance and...Performance and...Edit User Account and Azure SQL CPU at 100%Edit User Account and Azure SQL CPU at 100%
Previous
 
Next
New Post
3/1/2016 3:21 PM
 

How many users do you have?  I'm setting up a new DNN instance and am looking at somewhere between 150 and 900,000 DNN users depending on the way I set it up.  If performance is going to be an issue obviously I'll be leaning towards the lesser...

 
New Post
3/1/2016 8:08 PM
 
For simplicity, I would perform all the user management inside DNN.
DNN in general is able to handle hundred thousands of registered users -
however, with numbers larger than 10.000 users you should consider applying my Turbo Scripts.
We use it for clients with up to 200,000 registered users.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
3/4/2016 12:05 PM
 
I have less than 200 users. Probably about 20 really active users and 150-170 partially active.  The site is not really built around users, more toward anonymous access.  I upgraded from 5.6.8 to 7.4.2 and that is when I noticed the long delay bringing up the user account dialog to approve new users. My 5.6.8 installation was on a shared hosting provider that used shared SQL instances.  One thing I did was go through remove all unauthorized and deleted users which helped some. The delay is definitely longer when I first access a user after a restart (more than just a page recompile).  And in my local lab the CPU hits only 50 to 60%.  I know of DNN installations that handle many more users and seem to do okay, so not sure if this is an issue with having upgraded from 5.6.8, or with 7.4.2, or with Azure SQL. 
 
New Post
3/4/2016 3:25 PM
 
if you deleted a number of users, make sure you deleted user folders as well, which may affect performance significantly.
Besides, check database for largest tables and truncate log tables if they exceed a few thousand records.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
3/4/2016 5:18 PM
 

I used the User-Accounts page in Admin to delete unauthorized users and remove deleted users.  Where and how would I then delete the user folders?  And these were probably all users who were never authorized, so would they have a folder?

I have truncated the logs have the scheduler log cleared every night.  I also clear the event log each day.  I went through a whole long list of things to do to improve performance - compressed files, CDN media, removed unused modules etc. 

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Performance and...Performance and...Edit User Account and Azure SQL CPU at 100%Edit User Account and Azure SQL CPU at 100%


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out