Author: Tony Stewart
Subject: max CPU use= total cores / N per process , why?
Posted: 03 November 2014 at 5:26pm
Using Procexp to,view the % CPU per core is interesting but when Apps take maximum utilization, all versions of Windows( that I have used from XP to Win8x64) throttle the usage of most Apps to 25% of quad core and 50% of a dual core .
so would that be 12.5% of an 8 core? Is this intentional?
- there are exceptions, but this is my observation.
- then if I change CPU allocation on that App using ProcExp, it makes no difference to the total utilization, although a Quad Core will then go to 100% on that core.
When this occurs at a steady state for no good reason, I use ProcMon to find it in a tight loop read the same group registry keys for no good reason. Obviously there must be one, It doesn't seem to inhibit any major tasks in that process, but may be related to that it is polling states of system services or polling audio device state changes or some other useless task that does not seem to demand such processing power. bad code? DCOM inconsistencies? Visual Basic version errors like for MSVCR100.dll? No clues given in Procmon.
Subject: max CPU use= total cores / N per process , why?
Posted: 03 November 2014 at 5:26pm
Using Procexp to,view the % CPU per core is interesting but when Apps take maximum utilization, all versions of Windows( that I have used from XP to Win8x64) throttle the usage of most Apps to 25% of quad core and 50% of a dual core .
so would that be 12.5% of an 8 core? Is this intentional?
- there are exceptions, but this is my observation.
- then if I change CPU allocation on that App using ProcExp, it makes no difference to the total utilization, although a Quad Core will then go to 100% on that core.
When this occurs at a steady state for no good reason, I use ProcMon to find it in a tight loop read the same group registry keys for no good reason. Obviously there must be one, It doesn't seem to inhibit any major tasks in that process, but may be related to that it is polling states of system services or polling audio device state changes or some other useless task that does not seem to demand such processing power. bad code? DCOM inconsistencies? Visual Basic version errors like for MSVCR100.dll? No clues given in Procmon.