SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

One of our customers has a large SharePoint 2010 farm which was having problems with 100% CPU usage for a large part of every minute (15 seconds) when the Application Server Administration Service Timer Job was being run. The default schedule for the job is every minute, and although the web front ends were load balanced, the entire farm performed poorly due to such a large amount of time for each server being at 100% CPU. We have resolved the issue by changing the timer job to run every 10 minutes, but are concerned this may have side effects.

What side effects might we experience if the Application Server Administration Service Timer Job only runs every 10 minutes, instead of the default of 1 minute?

Thank you!

share|improve this question
Question is more like: What does this timer job precisely do? – Dribbel Feb 24 '12 at 13:40
I agree, although further analysis of what the job does as it relates to this particular environment is also appreciated. – dotnetengineer Feb 24 '12 at 14:05

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.