Windows任务管理器如何为进程分配优先级？

Hey there, let's dive into how Windows Task Manager handles process priorities—this is a topic with a few layers, so I'll break it down clearly.

First, it's key to understand that Windows uses a two-level system for scheduling:

• Process Priority Class: This is exactly what you adjust in Task Manager. It sets a baseline priority range for all threads within the process.
• Thread Priority Level: Each thread inside the process gets a priority offset relative to the process's class. The Windows scheduler uses this combined value to decide which thread gets CPU time first.

Task Manager exposes 6 priority classes you can set manually:

• Realtime: The highest possible priority—threads here will preempt almost all other processes, including critical system services. Use this extremely carefully, as it can freeze your system if misused.
• High: For processes that need immediate CPU time (e.g., audio/video editing tools that can't afford lag).
• Above Normal: Gives the process a slight boost over most background and regular apps.
• Normal: The default for 99% of user-facing apps and most system processes.
• Below Normal: For non-urgent background tasks (e.g., file sync tools, backup utilities).
• Low: The lowest priority class—only gets CPU time when no higher-priority threads are waiting. Perfect for things like idle-time virus scans.

By default, Task Manager doesn't "assign" priorities on its own—this is handled by Windows when a process launches:

• Most user applications start with the Normal priority class unless the program's code explicitly requests a different one.
• System-critical processes (like csrss.exe, wininit.exe) are assigned higher priority classes (often High) during boot to keep the system running smoothly.
• Background services are typically set to Below Normal or Low by default, so they don't interfere with foreground apps.

When you use Task Manager to change a process's priority, you're overriding this default class temporarily. The change only lasts until the process is closed or restarted—once you reboot or relaunch the app, it'll revert to its original default priority.

Windows uses a priority-based preemptive scheduler. Here's what that means in practice:

• Threads with a higher combined priority (class + thread offset) get picked to run before lower-priority ones.
• Even if a low-priority thread is running, a higher-priority thread will "preempt" it immediately when it's ready to run.
• Windows has a priority boosting mechanism: if a thread waits for an I/O operation (like reading from a disk or network) to complete, it gets a temporary priority boost once the operation finishes. This prevents low-priority threads from being starved of CPU time entirely.
• Realtime priority is a special case: it bypasses most of the system's scheduling safeguards. A realtime process can hog the CPU so much that even the Windows kernel's critical threads can't run—this is why you should only use it for specialized, short-lived tasks.

• Temporary changes only: As mentioned, Task Manager's priority edits don't stick across process restarts. To set a permanent priority, you'd need to modify the program's shortcut properties, use a registry tweak, or rely on third-party tools (but be cautious with these).
• Protected processes: Some system-critical processes (like svchost.exe instances running core services) can't have their priority changed via Task Manager—Windows blocks this to prevent system instability.
• Don't overuse Realtime: I can't stress this enough. Setting a regular app to Realtime can make your system unresponsive, as it'll take precedence over things like mouse input, display rendering, and system updates.

内容的提问来源于stack exchange，提问作者Shahid khan M