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...How Many Concurrent Users Can Be on a SiteHow Many Concurrent Users Can Be on a Site
Previous
 
Next
New Post
9/28/2010 4:14 PM
 
This is interesting to me because I am working on a somewhat similar site and a mid-level dedicated server from PowerDNN with 4 gb ram only handling 40 or so users is very scary!!

I'm taking a wild guess here but I would think the main issue is that you are writing to the sql database on every question answer x 40 users - that's a lot of trips to the database in a very short amount of time (71 answers x 40 users = 2,840 trips to database). Whereas if you "held your tongue"  and made only one trip to the database for all 71 answers at the end of the test you would reduce the amount of trips to the database greatly (40 trips to database) AND those trips would be spread out over a greater amount of time.

Don't know what you have built the test in but you could achieve the same "one question at a time" type of UI using either Dynamic Forms or XmodPro. This would also reduce the load on the web server since you would load the entire test on one page - you're just hiding most of the questions from user visibility until it comes time for them to see it.

Just some thoughts and please update this thread as you learn more.
 
New Post
9/28/2010 4:51 PM
 
from my experience, most of the database activity is NOT adding/updating records, but retrieving data, often the same data multiple times, if not properly cached. Every postback may request site, user, page and module data with settings, permissions, references, ... Switch caching to "heavy" in Host Settings and observe the results. Same applies to custom modules: if not caching data, questions might get retrieved for every question. This needs to be fixed in source code,. Last, check, which page the visitors are on - sometimes they do not behave as expected ;)

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
9/29/2010 5:59 AM
 
Hi Greg,
Unfortunately there isn't a guaranteed method to 100% predict how many concurrent users a server will handle, however, in most cases, it is a function of both the server and the DNN website itself.  The types of modules used really do have a big impact though - modules like the Text/HTML module perform much better under heavy load than form builder or other highly-dynamic modules.  If you're maxing out your CPU, I would recommend using a program like DotTrace or SQL Server Profiler to find out what DNN component is causing your CPU spike and then work on optimizing/replacing that component.

We have quite a handful of large customers who are getting 1000-1500 concurrent requests per web server (based on Mitch's math, this is 25k-75k "concurrent" users), however, these types of customers generally do a pretty in-depth analysis before adding any new module to their environment.  When you're handling that kind of load, a high-CPU module can mean the difference between needing 20 servers or needing 80 servers.

Even though you're in a single server environment, I would recommend taking a similar approach.  Knowing your environment, you should not expect to achieve the results above, however, by evaluating the modules that you're currently using, you should be able to increase your load.

 
New Post
9/29/2010 11:36 AM
 
Tony, thanks for jumping in on this thread. I just want to make it clear that I have been using PowerDNN servers for many years now and have been very satisfied. I don't want anyone to infer in any way that I think we have a problem with the server. This application that we have built is very important for this non-profit and my intent here is to acknowledge that there are things I don't know and to elicit feedback from the community. And I definitely got some good feedback. My ulterior motive of posting here was to get Mitchel to respond so that I could follow up with him offline and that worked out too. :) So I will be working with Mitchel in the coming week to do some testing and see how we can improve the configuration and application. I am not discounting the feedback from others on this thread because it was very helpful. I will provide more feedback after our testing next week. Thanks.

Forerunner Communications, LLC
DotNetNuke Integration Specialists

 
New Post
9/29/2010 11:47 AM
 
No clarification needed.  :-)  I know you have my cell number (its 402-650-6072 if anyone else on this thread wants it) and I know you'd be using it if you thought it was a problem with the server.  :-)

Depending on your customer's needs and the duration of the project, if, after Mitch takes a look at it, you still need more horsepower, let me know.  We could look at migrating you to a MiniGrid Cloud or a PowerGrid Cloud depending on your needs.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Performance and...Performance and...How Many Concurrent Users Can Be on a SiteHow Many Concurrent Users Can Be on a Site


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