Server Fault is a question and answer site for system and network administrators. 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

Our SharePoint development images are having performance problems. One of the developers has asked what timer jobs could be disabled. What prompted this was CPU time used by OWSTimer.EXE service.

share|improve this question

closed as primarily opinion-based by HopelessN00b Dec 5 '14 at 10:34

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

up vote 2 down vote accepted

I would disable none of them - they all server a purpose, be it for making sure workflows run correctly, auditing happens correctly, and "heavy"/"expensive" processes (like backups) happen at quiet times.

Having the CPU time high is not an indication of a problem though - you have the resources, so why not use them? If your users are complaining of slow speeds or you are seeing errors (timeouts in the event logs are common with SharePoint in situations where you do not have enough CPU) then you should look at scaling out your deployment.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.