 |
Vijilante SubAdmin

Joined: 18 Nov 2001 Posts: 5187
|
Posted: Sun Nov 18, 2007 5:18 pm
[2.12] PE Optimization |
I was observing some odd CPU usage spikes on my system from CMud. I finally tracked them down to having the mouse pointer in the tree panel of the Package Editor. Just in the panel, not pointing at anything. It might be that it is running a mouse over check for hints, but frequent spikes of 30%, with 60% occasionally, and a rare high of 80% doesn't quite seem right.
Procedure
1. Launch Taskmanager (CTRL-SHIFT-ESC)
2. Launch CMud
3. Close Sessions window (ESC)
4. Open Package Editor (CTRL-G)
5. Move the mouse pointer into the tree panel of the PE anywhere below the untitled window setting
The spikes have a rather regular interval, and don't occur when the mouse pointer is somewhere outside of that panel. |
|
_________________ The only good questions are the ones we have never answered before.
Search the Forums |
|
|
 |
Tech GURU

Joined: 18 Oct 2000 Posts: 2733 Location: Atlanta, USA
|
Posted: Sun Nov 18, 2007 6:51 pm |
I'm not seeing this. I've only seen spikes around 10 to 13% and I've got a lot of windows open. I'm on Thinkpad T60p with a Core Duo processor.
|
|
_________________ Asati di tempari! |
|
|
 |
Vijilante SubAdmin

Joined: 18 Nov 2001 Posts: 5187
|
Posted: Sun Nov 18, 2007 7:41 pm |
Your spikes of 10-13% are about equivalent to my 30% spikes. I have a nice ancient 1GHz Athalon. The point really is that the program should be doing practically nothing with the above procedure and the CPU should be sitting almost continuously idle.
|
|
_________________ The only good questions are the ones we have never answered before.
Search the Forums |
|
|
 |
Seb Wizard
Joined: 14 Aug 2004 Posts: 1269
|
Posted: Wed Nov 21, 2007 3:26 am |
I reported this way back in CMUD 1.0x. Zugg said he couldn't do much about it or that it was low priority.
|
|
|
|
 |
Zugg MASTER

Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Wed Nov 21, 2007 4:01 am |
Yep, Seb is correct. We just have to hope it magically goes away when I update the DevExpress components (which is going to be next year now).
|
|
|
|
 |
|
|
|