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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsForumForumSolution for DNN Slow sitesSolution for DNN Slow sites
Previous
 
Next
New Post
2/15/2016 4:49 AM
 

Hi,

I am using DNN 6. I have hundreds of child sites.

It is working fine and fast when I am editing/adding something.

but

When I am trying to Run a wizard to create a child site, then it gives hosing error or it gets slow down.

Any solution for this?

 

Regards,

 
New Post
2/15/2016 5:55 AM
 
The website wizard has been rarely used and the Create Site process is for sure not optimized for performance.
You may use SQL Server Profiler to monitor the database calls and identify the one which consumes the most time.
Report it back and I'll check for improvement options.

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/16/2016 7:38 AM
 

Thanks for the reply.

I am working on SQL server profiler. I'll update you on this for improvement options.

I have read somewhere to truncate tables eventlog and sitelog 

because entries are added to the sitelog table for each page request and entries are written to the eventlog table for system events.

So, do I truncate these two tables and it will help me?

 

Regards,

 
New Post
2/16/2016 11:46 AM
 
I think it is incredibly unlikely that those tables have any measurable effect on this one use case.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
2/16/2016 12:21 PM
 
it depends on the size of your database and transaction log. If it exceeds 100 MB, it might be worth checking the largest tables, if they are SiteLog, you might consider truncating it (or turn it off, if you don't use it), if it is table EventLog or Exceptions, you might need to truncate these tables (see http://www.dnnsoftware.com/community-...). Similar applies to table Schedule History. If Transaction log file reaches its limit, you need to truncate it (using backup or shrink file). You might consider switching recovery model to "simple", if you are still using "full".

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsForumForumSolution for DNN Slow sitesSolution for DNN Slow sites


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.

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out