Home »
Windows
»
Windows Oddities
Summary: Can a computer really do nothing? Yes and no. When it's doing nothing it has to do something, and that something is the System Idle Process.
|
What is the System Idle Process and why is it using 96 to 99% of the CPU? |
This is a great example of things we geeks probably take for granted, that's not always obvious to the rest of the world.
I mean, really, a process that regularly takes up 99% of your CPU's time must be a bad thing, right?
Nope, not at all. Just the opposite, in this case.
•
First, let me show you what we're talking about.
Firing up Windows Task Manager, and then clicking on the "CPU" column to sort by CPU Usage, (click again to reverse the sort order if all you see are zeros in that column) you'll often see something like this:

You can see that something called "System Idle Process" is taking up a full 92% of my CPU's resources.
Seems like a lot, so what's up with that?
The fact is that most computers can never really do nothing. When the computer is on, the CPU's running and it must do something - even if that "something" is waiting for something real to do.
Think of it as your computer just twiddling its virtual thumbs, waiting for something more important to do. The computer's doing something (virtual thumb twiddling), but we wouldn't call that doing anything useful.
That's called being idle.
And the "System Idle Process" is the software that runs when the computer has absolutely nothing better to do.
It effectively runs at the lowest possible priority so that if anything, anything at all, comes along for the CPU to work on, it can. When there's nothing left to do, back to idle it goes.
So having the System Idle Process using 90% of your CPU is a good thing ... it means that that 90% is readily availble should there be any real work to do.
Related:
Ask Leo! - How do I find out what program is using all my CPU?
Ask Leo! - How do I find out who's using all my memory?
Article C3322 - March 17, 2008
Hi
Posted by: David Hawkins at March 22, 2008 2:41 AMThe Idle Process can kick in when you are engaged in when you are using Movie Making software and are downloading or writing video causing you to lose or get distorted clips or frames. To get around this you can deliberately start the Idle Process so that it effectively gets it out of the way and won't start up in the middle of your movie making. You can also use a little program called "End It All" which also helps, but thats a different thread.
David
Simon said: "which raises the question of what the CPU would be doing that would use power if the OS *didn't* continually issue these HLT commands."
Adding 0 to 0. Repeatedly. :)
Actually, that's a joke. What it would do is check over and over again if anything's happening, like a key being pressed or the like. Read http://en.wikipedia.org/wiki/Busy_waiting (and http://en.wikipedia.org/wiki/HLT while you're at it).
Also, thanks for pushing me to research this :)
Posted by: Octav at March 22, 2008 6:37 PMSometimes my machine is running idle and it cannot be interrupted. That is, the idle process is too busy to notice keystrokes and mouse clicks.
Leo, do you know why this is happening?
I once read something about WinXp automatically moving files about, a kind of optimisation. When I can't interrupt the idle process there is certainly a lot of disk processing (I can hear the heads thrashing). I haven't been able to find the information about automatic file positioning again and sometimes wondering if it was a figment of my imagination.
Posted by: Greg Webb at March 23, 2008 2:56 PMThe point seems to be that users expectations are that the SIP should not take over the machine, but it does, interferring with the usefulness of the computer. There have been many times for me when a program has appeared to have crashed when in fact the computer is just busy doing the SIP. If the SIP is housekeeping processes and commands to keep the processor occupied during periods when programs are inactive then as soon as a program requires the CPU, the SIP should be suspended. So either the SIP has been badly programmed or it is more than the computer sorting itself out. Either way this is very frustrating to users and a way to control the SIP would be really welcome.
-Leo
On my computer i found the same thing, but while transferring a massive 120 gb folder from partition to partition. Needless to say it is deadly slow, should,nt the processor consider that an opportunity to maximize the cpu to decrease time? Or did i miss something here, =)
06-Feb-2009
Leo, I understand what you are saying about SIP not interfering by definition, or by design is probably better. But what Hawkins, Webb, and Milton are saying is true. In practice, I have often noticed momentary hangs in the application I'm working with when SIP kicks in (this is XP SP2). Whatever the intent, SIP does in fact interfere. What is needed, as Milton says, is user control of this feature.
21-Feb-2009
I read the above article and I understand the virtual thumb twiddling bit SIP doesn't stop when I try to start another program. Is it that once it starts, it must finish the SIP first? Is this process only characteristic of Windows?
25-Feb-2009
This is one of the few posted answers that uses "resources" instead of "usage" or "processing" But may still leave some in the dark. The CPU column next to "Image Name" in task manager(as in posted pic) is NOT the cpu "Usage" it refers to cycles to the processor(instructions that let it know whats goin on, on the system - kinda like the dispatcher of your local taxi company) In this case the System Idle gets all the dispatcher attention when your system is doing nothing. Although it cant be seen on the edited posted pic, at the bottome of task manager is the ACTUAL cpu "USAGE" When the cpu "USAGE" goes up the Idle "CYCLES" go down and vise versa. So when the "CYCLES"(shown in pic) are in the 90's your cpu "USAGE" should be low 0-10%. If you are seeing both #'s high there may be other issues. As far as some of the post with jerkiness I beleive that is an XP IDE problem itself. I have used 2k til 08 when forced to upgrade due to newer hardware and have had that problem as well, EVEN when my actual cpu "USAGE" has been under 10%.
Posted by: PcJedi240 at March 3, 2009 10:14 PMIn closing the high "CYCLES" are normal on SysIdle if you have constant maxed "USAGE" (bottom of task manager)then you have something goin on but the high "Cycles" arent it.
My "system idle process" has been running from 95 to 99 since Friday....5 days....and I have just been able to sign on the internet tonight (Tuesday night). Don't understand this.....and even though I can sign onto the internet now, this "thing" still seems to control what I can and cannot do.....Richard
16-Mar-2009
Leo, don't worry these guys will never get it.
The System Idle Process is not actually a process, it's a representation of the CPU that is not being used.
I.E. You have firefox running at 5% cpu usage constantly and nothing else is above 0% the System Idle Process will read 95% usage because it's the inverse of the amount being used... it's not actually using 95% of your CPU (it does nothing and serves no purpose except to show what is not being used).
The problem most people are referring to is more than likely to be Intel SpeedStep or AMD's Cool n Quiet technology, both of which throttle the CPU clock speed (and sometimes voltage) when the computer is inactive (idle) if enabled.
Posted by: kittonkicker at April 23, 2009 2:31 AM