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...5.5.1 fresh installs - excessive time outs and slow performance5.5.1 fresh installs - excessive time outs and slow performance
Previous
 
Next
New Post
10/12/2010 7:51 AM
 
do you experience issues with the database performance? did you check the DNN event viewer (in admin menu) for other related issues?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/12/2010 10:20 AM
 
Ed Jankauskas wrote:
I see from the other posts that there are the same issues with speed that I am experiencing. I am also timing out like crazy on two new 5.5.1 site I just put up. I am using KeepAlive and can't believe all the non-responsive time out errors that I am receiving. Is there anyone who has found a setting or two that can be tweaked? I tried truncating the database and that doesn't help. Is thins just a 5.5.1 bug, or a memory hog issue? I am on a shared hosting provider that placed my sites in dedicated app pools and it is so expensive to add dedicated resources.  If it is a memory hog, what is the best previous release that doesn't have speed and time-out issues? Thanks!

Putting a DNN site on a dedicated pool ON SHARED HOSTING is slowing things down, because usually the memory size is not more than 32k (or less). Ask your hoster the pool size.

Have you changed the caching to Heavy ? Do you use disk or memory for paging ? Is the SQL server ok, because usually the timeouts come from the SQL. Not always but usually.

 
New Post
10/12/2010 3:02 PM
 
Sebastian Leupold wrote:
do you experience issues with the database performance? did you check the DNN event viewer (in admin menu) for other related issues?

I have my hosting provider checking the database. Per your suggestion in another post, I also am having them check if the latest .NET security patch is applied to my webserver. Here are the other error types I see in the event viewer:

DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 90540359-ff34-449c-a63f-12bdac958fc3
InnerException: This operation returned because the timeout period expired. (Exception from HRESULT: 0x800705B4)
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Threading.ReaderWriterLock.AcquireReaderLockInternal
StackTrace:
Message: System.ApplicationException: This operation returned because the timeout period expired. (Exception from HRESULT: 0x800705B4) at System.Threading.ReaderWriterLock.AcquireReaderLockInternal(Int32 millisecondsTimeout) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.get_ScheduleInProgress()

These two are related:

THREAD ID: 1014
TYPE: DotNetNuke.Services.Search.SearchEngineScheduler
EXCEPTION: Thread was being aborted.
RESCHEDULED FOR: 1/1/0001 1:00:00 AM
SOURCE: STARTED_FROM_BEGIN_REQUEST
ACTIVE THREADS: -1
FREE THREADS: 2
READER TIMEOUTS: 0
WRITER TIMEOUTS: 0
IN PROGRESS: 0
IN QUEUE: 5
Server Name: DNPWEB2-TX2

DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: e333c1d5-99fb-42c3-9415-ed8183aeac4d
InnerException: Thread was being aborted.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Services.Scheduling.DNNScheduling.CoreScheduler.WorkStarted
StackTrace:
Message: System.Threading.ThreadAbortException: Thread was being aborted. at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.WorkStarted(SchedulerClient& objSchedulerClient) at DotNetNuke.Services.Scheduling.SchedulerClient.Started() at DotNetNuke.Services.Scheduling.DNNScheduling.ProcessGroup.Run(ScheduleHistoryItem objScheduleHistoryItem)
Source:
Server Name: DNPWEB2-TX2

 
New Post
10/12/2010 3:17 PM
 
Is that Net 2 (3.5) or Net 4 ? The Scheduler errors are something i have seen also in ALL my DNN installations latety. So i have switched back to Net 2 (3.5) because i do suspect this is the cause. But the scheduler error can be put off, just go in the schedule options and make those to happen daily or something. Those errors alone can't timeout your whole DNN portal.
 
New Post
10/12/2010 3:53 PM
 
It's NET 2 (3.5). Thanks for that info Dimitris. I'll get rid of the scheduler.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Performance and...Performance and...5.5.1 fresh installs - excessive time outs and slow performance5.5.1 fresh installs - excessive time outs and slow performance


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