I am trying to make a DNN-based custom application run as fast as possible and be as scalable as I can make it. So I have been using DotTrace (as a novice) to try to find resource hogs. At first it was my menu system. I realized that the menu isn't used by the application end users so I removed it totally in a version of the skin for end users. It is still there for application administrators. Then I removed all the extra DNN components on the page like Search, Breadcrumb, Current Date, Copyright, etc. Things seem to be looking pretty good but I won't know until we load in a significant number of users and test.

At this point the only thing that looks like a resource hog is the  DNN Scheduler. I see these two functions at the top of my list in DotTrace.

DotNetNuke.Services.Scheduling.DNNScheduling.DNNScheduler.Start()

DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler+CoreScheduler.Start()

I turned my scheduler mode to Disabled for now and the performance numbers dropped really low.

So my question is what if any are the negative implications of leaving the Scheduler Mode in disabled? If there are long term issues, then what about short term disabling of the scheduler? The application is used on a scheduled basis (no pun intended) so I could turn off the scheduler when expecting a heavy load and then turn it back on.

Thanks for any guidance you can provide.