I just wanted to ask that what is the reason behind making the maximum utilization of the processor ,that is ,whenever at any instant of time ,the scheduler makes sure that the processor must not remain idle and it must always be in the process of executing some process,so does that not require more power to be consumed by the processor.

So basically what is the reason behind always making the processor run,what would be the drawback if the processor remains idle,will that not save the power consumed by the processor.

closed as primarily opinion-based by Ramhound, bwDraco, sawdust, mdpc, DavidPostill Jan 19 '15 at 8:25

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.

  • 2
    I believe that the windows-task-scheduler tag is inappropriate... Anyway the question is really strange and I wonder if you just may have not made yourself clear :) – Vitas Jan 18 '15 at 20:48
  • Why does an employer want the maximum productivity out of an employee or a ROI (return on investment) for a piece of capital equipment? If you don't care about maximizing utilization, then go back to batch processing or a single-user PC running non-multitasking MS-DOS. – sawdust Jan 19 '15 at 1:58

It's a matter of priorities. I don't mean thread or process priorities. I mean - what's more important? Getting work done, or saving power?

If getting work done is more important - and btw, in what you described, that is apparently the case - then if there's work to do, you want the processor doing that work. An idle processor is a wasted processor, just like "free" RAM is wated RAM.

Now if saving power is more important than getting work done, then you use a scheduling algorithm that takes that into account.


Maximum CPU utilization is not per se a major objective of scheduling algorithms. It is just a side effect of an obvious scheduling algorithm objective which is to keep the runnable processes waiting queue as short as possible.

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