Threads are often scheduled to execute on CPU 0
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 39%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
soundex
0
Reputation points
The execution of the encode thread of our program is very time-consuming. Using WPR to record the CPU usage, and opening it with WPA, it is found that the execution time of the thread on CPU 0 is too long. The remote desktop connects to the computer, the execution time on CPU 0 becomes shorter, and the encoding thread returns to normal. In addition, turn off CPU 0 in Task Manager-set affinity , and the encode thread can also return to normal.
CPU：11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz 2.42 GHz
System：Windows10 21H2 19044.1288
abnormal:
normal(the execution time on CPU 0 becomes shorter):
Windows for business | Windows Client for IT Pros | User experience | Other
{count} votes
-
soundex 0 Reputation points
2023-06-28T06:18:47.98+00:00 It is normal for our program to be installed on other computers.
CPU：Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz 2.90 GHz
System：Windows10 22H2 19045.2965
-
soundex 0 Reputation points
2023-06-28T09:44:19.8166667+00:00 or Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz 3.19 GHz
Sign in to comment
Sign in to answer