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...Administration ...Administration ...Schedule tasks retain more rows than specifiedSchedule tasks retain more rows than specified
Previous
 
Next
New Post
1/12/2007 6:26 AM
 

Hi,

(sorry if this post is duplicated, I have had problems with the first try).

I have had lots of performance problems these last 3 weeks and I've found that they come from the ScheduleHistory table that grows beyond the specified limits.

What I mean is that there are two tasks: PurgeUsersOnline and PurgeLogBuffer that are configured to retain only 60 rows but they have far more rows (they reached even 2000). These tasks are scheduled to run every 1 minute; of course I can change that value, but: how come they have more than 60 rows??

If I run this SQL:

select ScheduleHistory.ScheduleID, Schedule.TypeFullName, Schedule.TimeLapse, Schedule.TimeLapseMeasurement, Schedule.RetainHistoryNum, count (*) as row_count
from ScheduleHistory join Schedule on (ScheduleHistory.ScheduleID = Schedule.ScheduleID)
group by ScheduleHistory.ScheduleID, Schedule.TypeFullName, Schedule.TimeLapse, Schedule.TimeLapseMeasurement, Schedule.RetainHistoryNum

I get the following result:

ScheduleID TypeFullName TimeLapse TimeLapseMeasurement RetainHistoryNum row_count
3 DotNetNuke.Services.Scheduling.PurgeScheduleHistory, DOTNETNUKE 1 d 60 60
6 DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE 30 m 60 60
9 DotNetNuke.Services.Cache.PurgeCache, DOTNETNUKE 2 h 10 44
12 ActiveModules.Forums.MailConnector.MailConnectorScheduler, ACTIVEMODULES.FORUMS.MAILCONNECTOR 2 m 60 60
7 DotNetNuke.Modules.Admin.ResourceInstaller.InstallResources, DOTNETNUKE 30 m 60 320
1 DotNetNuke.Entities.Users.PurgeUsersOnline, DOTNETNUKE 1 m 60 2061
4 DotNetNuke.Services.Log.EventLog.PurgeLogBuffer, DOTNETNUKE 1 m 60 1962
2 DotNetNuke.Services.Log.SiteLog.PurgeSiteLog, DOTNETNUKE 1 d 10 11
13 XepientSolutions.XSSearchSpider.XSSearchSpider, XepientSolutions.XSSearchSpider 4 d 5 8
5 DotNetNuke.Services.Log.EventLog.SendLogNotifications, DOTNETNUKE 5 m 60 820
8 DotNetNuke.Services.FileSystem.SynchronizeFileSystem, DOTNETNUKE 1 h 10 10

My site is using DNN 4.40. What is it going wrong?

Thanks in advance,

Pablo.

 
New Post
1/12/2007 9:55 AM
 

Well, I have found the way to solve it.

If I configure the schedule task "PurgeScheduleHistory" to run every 15 minutes, it takes care of removing the exceeding rows of each task.

So I was wrong thinking that each task is responsible of removing its old rows. The only task that keeps the right amount of rows is "PurgeScheduleHistory". If you don't run it frequently, your ScheduleHistory table grows and your DNN dedicates the whole cpu time to SQL Server.

Hope it helps someone else!

Pablo. 

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Schedule tasks retain more rows than specifiedSchedule tasks retain more rows than specified


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