Brief description of your issue
I discovered that the CPU relative usage number is affected by the affinity settings, which makes the number very unintuitive. For example, on my 64-thread machine, I'm pinning one process to 16 logical CPUs (one NUMA node) and letting it use all 16 of it, and full CPU usage by the process should be 1600, but as the affinity is applied to it again, it will only show as 400 usage.
Steps to reproduce (optional)
Have a process to use a subset of cores and set the CPU affinity to that number of cores.
Expected behavior (optional)
The relative CPU usage should still show as one core usage as 100.
Actual behavior (optional)
The actual displayed relative usage is multiplied by affinity settings.
Environment (optional)
SI 3.2.25347.754 canary
Windows 10
Brief description of your issue
I discovered that the CPU relative usage number is affected by the affinity settings, which makes the number very unintuitive. For example, on my 64-thread machine, I'm pinning one process to 16 logical CPUs (one NUMA node) and letting it use all 16 of it, and full CPU usage by the process should be 1600, but as the affinity is applied to it again, it will only show as 400 usage.
Steps to reproduce (optional)
Have a process to use a subset of cores and set the CPU affinity to that number of cores.
Expected behavior (optional)
The relative CPU usage should still show as one core usage as 100.
Actual behavior (optional)
The actual displayed relative usage is multiplied by affinity settings.
Environment (optional)