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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Problems with DNNProblems with DNN's SearchEngineScheduler
Previous
 
Next
New Post
4/3/2008 5:38 PM
 

I've had problems with the scheduled task used to run the Search Engine Scheduler (e.g., DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE)

Having it running as a scheduled task seemed to be causing performance issues and it seemed like it had a memory leak when another member of my team was reviewing it .  Is anyone else experiencing similar results? 

We turned the task off for the last 4 months and the performance issues we had haven't occurred since.  However, we have customers that want to use this feature, so I'm researching a solution and considering turning it back on. On my test server I'm seeing performance degradation again since the task has been turned back on and it isn't completing successfully.  

Is there a manual stored procedure that I can run in order to get this feature working again? Any ideas or information on this would be helpful.

Thanks in Advance!

 
New Post
4/14/2008 10:23 PM
 

The search engine schedule is not very good in my opinion.. It takes a long time, and you need to be very careful to get its settings correct..  The bigger your site, the longer it takes.   If it starts taking longer than the retry interval, then you will have problems.

The first thing to do is change the scheduler to use Timer Method (host settings page).. this at least gives the schedule a separate thread and improves the performance..

JK.

 


You know your website is cool, so why not let your users help you by spreading the word on social networking sites - get the DotNetNuke Social Bookmarks Module with 57 different ways to add social bookmarks to your site ... or download the FREE demo right now
 
New Post
4/15/2008 10:58 AM
 

I have worked with many clients to get the performance of this in check without actual modifications to the code.

As the person above mentioned I would be sure that your scheduled tasks are running in Timer Mode.

Also, from the sounds of it you have a big site, set the interval on the task to be 24 hours, that way it only goes once per day, you still get updates but it will be better.  Then after it has ran have a look at the history to see the total execution time, and then you can tweak the run time accordingly.  If you need more details, feel free to drop me a message as we help clients with this type of issue all the time msellers@iowacomputergurus.com


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
4/24/2008 1:23 PM
 

We are having some of the same problems with the scheduler and the SearchEngineScheduler. We have the scheduler set to Timer mode. We also have our DNN sites split out amongst 4 or 5 applications pools in IIS 6. Does this mean that a scheduler thread will be started for each app pool? The reason i ask is that when i look at the history of the SearchEngineScheduler, it looks like the scheduled item is running numerous times. We the SearchEngineScheduler set to run once a day with no catch up or retry interval. For example, this is from the SearchEngineScheduler history from last night. Also, before these that i pasted below, there were 25-30 failed attempts. Thanks!

Description Duration (ms) Succeeded Start/End/Next Start
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
190.706 True S: 4/23/2008 9:50:10 PM
E: 4/23/2008 9:53:21 PM
N: 4/24/2008 9:50:10 PM
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
193.674 True S: 4/23/2008 9:50:09 PM
E: 4/23/2008 9:53:23 PM
N: 4/24/2008 9:50:09 PM
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
327.316 True S: 4/23/2008 9:44:27 PM
E: 4/23/2008 9:49:55 PM
N: 4/24/2008 9:44:27 PM
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
347.303 True S: 4/23/2008 9:43:54 PM
E: 4/23/2008 9:49:41 PM
N: 4/24/2008 9:43:54 PM
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
335.85 True S: 4/23/2008 9:43:45 PM
E: 4/23/2008 9:49:21 PM
N: 4/24/2008 9:43:45 PM
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
381.26 True S: 4/23/2008 9:42:09 PM
E: 4/23/2008 9:48:30 PM
N: 4/24/2008 9:42:09 PM
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
496.01 True S: 4/23/2008 9:36:06 PM
E: 4/23/2008 9:44:22 PM
N: 4/24/2008 9:36:06 PM
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
501.96 True S: 4/23/2008 9:35:09 PM
E: 4/23/2008 9:43:31 PM
N: 4/24/2008 9:35:09 PM
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
516.663 True S: 4/23/2008 9:35:06 PM
E: 4/23/2008 9:43:43 PM
N: 4/24/2008 9:35:06 PM
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
519.963 True S: 4/23/2008 9:35:03 PM
E: 4/23/2008 9:43:43 PM
N: 4/24/2008 9:35:03 PM
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
448.773 True S: 4/23/2008 9:34:28 PM
E: 4/23/2008 9:41:56 PM
N: 4/24/2008 9:34:28 PM
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
479.367 True S: 4/23/2008 9:34:27 PM
E: 4/23/2008 9:42:26 PM
N: 4/24/2008 9:34:27 PM
 
New Post
4/24/2008 2:13 PM
 

If all those App Pools are pointing at the same DNN Install then the answer is yes.

You don't want to have more than one asp.net worker process pointing at a single DNN installation or you will have this problem.


DotNetNuke Modules from Snapsis.com
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Problems with DNNProblems with DNN's SearchEngineScheduler


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