![]() |
ProcExp showing higher CPU usage than Task Manager |
Post Reply
|
Page <123 |
| Author | |
wj32
Senior Member
Joined: 16 January 2009 Location: Australia Status: Offline Points: 1016 |
Post Options
Thanks(0)
Quote Reply
Posted: 15 July 2011 at 7:46am |
I have a Q6600. At 66%, I get around 9.4 billion cycles/sec for all processes combined (including Idle), and around 9.2 billion cycles/sec for Idle. If I force the frequency to be 97%, I get the same numbers. I really have no idea why this problem occurs, since on Intel CPUs since "Core" (or even earlier) the RDTSC instruction should increase at a constant rate with respect to wall time. Even if the time stamp counter was slowed down, I don't see why that would lead to just Idle having fewer cycles/sec than usual. But I'm just speculating here. ![]() |
|
|
PH, a free and open source process viewer.
|
|
![]() |
|
romkyns
Newbie
Joined: 06 September 2010 Status: Offline Points: 31 |
Post Options
Thanks(0)
Quote Reply
Posted: 02 August 2011 at 12:07pm |
|
I use the PE tray icon on my laptop as an indicator of "something is eating lots of your battery". Version 14.1 and above fail miserably at showing how much CPU is actually being consumed, in "absolute" terms.
For example, by showing the current frequency as a % on the very same usage graph, like the Resource Monitor so cleverly does: ![]() It's immediately obvious (to someone who knows the colors) that the CPU is running at 55% capacity, and that 20% of the max capacity (which is roughly a third of the current capacity) are being used by software. Pretty please for v16 of Process Explorer: do this too, and revert to the "normal" CPU usage value throughout PE. It's just silly that Process Explorer does so much worse a job of visualizing CPU usage than standard Win7 software! Edited by romkyns - 02 August 2011 at 12:24pm |
|
![]() |
|
mikelonergan
Newbie
Joined: 28 August 2005 Location: United States Status: Offline Points: 10 |
Post Options
Thanks(0)
Quote Reply
Posted: 27 August 2011 at 7:36pm |
Exactly my usage of PE as well - laptop battery consumption indicator. I've been concerned about this for months, assumed it was a bug in PE, figured it would eventually get flushed out of the code. Now I find out that the app is just really terrible at *reporting*? That I can no longer rely on it as a means of telling me when my system has been taken over by runaway processes or other CPU-intensive operations that I don't want? Well, back to v14.0 for me until Mark & co get a clue that it doesn't matter how technically "right" this is - it's just not a *useful* metric and we're going to have to go elsewhere (or elsewhen) to get the kind of information we used to expect (and rely on implicitly) from PE.
|
|
![]() |
|
zakk
Groupie
Joined: 13 June 2008 Status: Offline Points: 73 |
Post Options
Thanks(0)
Quote Reply
Posted: 12 October 2011 at 4:21pm |
|
I hope that the previous way of calculating cpu will be added again to Process Explorer, as an extra option.
I find it confusing the way it currently is - I've restored the forgottten windows task manager (removed Process Explorer's association ) for this particular reason... PS. I have windows 7 x64 and the cpu is Intel Mobile Core2 Duo T5870 @2.00GHz. Edited by zakk - 12 October 2011 at 4:30pm |
|
![]() |
|
romkyns
Newbie
Joined: 06 September 2010 Status: Offline Points: 31 |
Post Options
Thanks(0)
Quote Reply
Posted: 05 December 2012 at 12:01pm |
|
If you're hoping that maybe this bug has been fixed in the last year... dream on.
![]() Mark, why are you so set on making it impossible to use the latest ProcExp versions? Do you really, honestly think the above output makes any sense whatsoever? I don't buy the "different calculation" argument: if you go to the System Information window, individual core graphs work correctly. All that's needed to fix this is to add up whatever numbers you show for individual cores. There's no excuse for this bug. For users: if you're affected by this bug, you did nothing wrong. Just go back to v14.1 until this is fixed. Except if you're on Win8, then you're SOL. Edited by romkyns - 05 December 2012 at 12:37pm |
|
![]() |
|
Astara
Senior Member
Joined: 11 August 2005 Location: California, USA Status: Offline Points: 111 |
Post Options
Thanks(0)
Quote Reply
Posted: 11 December 2012 at 12:00am |
|
You might try http://sourceforge.net/projects/processhacker/.
Tried it when PE development all but ceased. |
|
![]() |
|
romkyns
Newbie
Joined: 06 September 2010 Status: Offline Points: 31 |
Post Options
Thanks(0)
Quote Reply
Posted: 12 December 2012 at 11:40am |
|
Indeed, Astara. I've been using it for almost a week now and wow, has it caught up feature-wise since the last time I tried it! About the only thing I miss is the "target marker" feature, to jump to a process by pointing at a window. There's probably a plugin for that, I should try searching for one.
Pity how ProcExp wasn't open-source and all that work had to be re-done from scratch. Edited by romkyns - 12 December 2012 at 11:41am |
|
![]() |
|
wj32
Senior Member
Joined: 16 January 2009 Location: Australia Status: Offline Points: 1016 |
Post Options
Thanks(0)
Quote Reply
Posted: 13 December 2012 at 7:43am |
At the risk of this being completely off-topic: it's the little window icon on the toolbar, when you enable the ToolStatus plugin. |
|
|
PH, a free and open source process viewer.
|
|
![]() |
|
MagicAndre1981
Moderator Group
Joined: 08 January 2007 Location: Germany Status: Offline Points: 1456 |
Post Options
Thanks(0)
Quote Reply
Posted: 13 December 2012 at 7:24pm |
|
@wj32
a bit OT, but I can't compile the latest SVN version. |
|
![]() |
|
Post Reply
|
Page <123 |
|
Tweet
|
| Forum Jump | Forum Permissions ![]() You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |