Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
System Idle Process
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{Short description|Kernel process in Windows NT operating systems}} {{Multiple issues| {{refimprove|date=July 2012}} {{primary sources|date=July 2012}} {{no footnotes|date=July 2012}} }} {{Infobox software | name = System Idle Process | screenshot = System idle process.png | screenshot_size = 300px | caption = [[Windows Task Manager]] in [[Windows XP]] showing System Idle Process usage at 99%, indicating that no other process is using significant CPU time. | operating system = [[Microsoft Windows]] | genre = Kernel }} In [[Windows NT]] operating systems, the '''System Idle Process''' contains one or more kernel [[Thread (computer science)|threads]] which run when no other runnable thread can be scheduled on a CPU. In a multiprocessor system, there is one idle thread associated with each CPU core. For a system with [[hyperthreading]] enabled, there is an idle thread for each logical processor. The primary purpose of the idle process and its threads is to eliminate what would otherwise be a special case in the scheduler. Without the idle threads, there could be cases when no threads were runnable (or "Ready" in terms of Windows scheduling states). Since the idle threads are always in a Ready state (if not already Running), this can never happen. Thus whenever the scheduler is called due to the current thread leaving its CPU, another thread can always be found to run on that CPU, even if it is only the CPU's idle thread. The CPU time attributed to the idle process is therefore indicative of the amount of CPU time that is ''not'' needed or wanted by any other threads in the system. The scheduler treats the idle threads as special cases in terms of thread scheduling priority. The idle threads are scheduled as if they each had a priority lower than can be set for any ordinary thread. Because of the idle process's function, its CPU time measurement (visible through, for example, [[Windows Task Manager]]) may make it appear to users that the idle process is monopolizing the CPU. However, the idle process does not use up computer resources (even when stated to be running at a high percent). Its CPU time "usage" is a measure of how much CPU time is not being used by other threads. In Windows 2000 and later the threads in the System Idle Process are also used to implement [[CPU]] power saving. The exact power saving scheme depends on the operating system version and on the hardware and [[firmware]] capabilities of the system in question. For instance, on [[x86]] processors under Windows 2000, the idle thread will run a loop of [[HLT (x86 instruction)|halt]] instructions, which causes the CPU to turn off many internal components until an [[interrupt request]] arrives. Later versions of Windows implement more complex CPU power saving methods. On these systems the idle thread will call routines in the [[Hardware Abstraction Layer]] to reduce CPU clock speed or to implement other power-saving mechanisms. There are more detailed sources of such information available through Windows' performance monitoring system (accessible with the perfmon program), which includes more finely grained categorization of CPU usage. A limited [[subset]] of the CPU time categorization is also accessible through the [[Windows Task Manager|Task Manager]], which can display CPU usage by CPU, and categorized by time spent in user vs. kernel code. == See also == * [[List of Microsoft Windows components]] * [[Idle (CPU)]] * [[Microsoft Windows]] * [[HLT (x86 instruction)]] * [[Process Explorer]] == References == * {{cite book | title = Microsoft Windows Internals | edition = 4th | chapter = Chapter 2: System Architecture | pages = [https://archive.org/details/isbn_9780735619173/page/75 75β76] | last = Russinovich | first = Mark | author-link = Mark Russinovich | author2 = David A. Solomon | year = 2005 | publisher = Microsoft Press | isbn = 0-7356-1917-4 | url-access = registration | url = https://archive.org/details/isbn_9780735619173/page/75 }} * {{Cite web|title=What Is "System Idle Process," and Why Is It Using So Much CPU?|url=https://www.howtogeek.com/411569/what-is-system-idle-process-and-why-is-it-using-so-much-cpu/|access-date=2022-01-13|website=How-To Geek|date=25 April 2019 |language=en-US}} * {{Cite web|title=system idle process - What is system idle process?|url=https://www.processlibrary.com/en/directory/files/system%20idle%20process/25540/|access-date=2022-01-13|website=www.processlibrary.com}} {{Windows Components}} [[Category:Windows NT architecture]]
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)
Pages transcluded onto the current version of this page
(
help
)
:
Template:Cite book
(
edit
)
Template:Cite web
(
edit
)
Template:Infobox
(
edit
)
Template:Infobox software
(
edit
)
Template:Main other
(
edit
)
Template:Multiple issues
(
edit
)
Template:Short description
(
edit
)
Template:Template other
(
edit
)
Template:Windows Components
(
edit
)