CPU Usage

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
Jul 13, 2009
44
0
#1
TCC 14.03.59 x64 Windows 7 [Version 6.1.7601]
Hello,
I have three tcc.exe tabs open, with TakeCommand minimized in the taskbar. I am not running any programs or batch file in any of the tabs.
When I look at TaskManager, I generally see that each tab is getting ~5% of the CPU.
What are they doing?
Curious ---
 
#3
It's unlikely they're doing anything. It's more likely that you have another app that's injecting something into TCC.EXE.
I don't see any CPU usage, but I noticed that with one tab open, TCMD's "Page Fault Delta" (page faults per second (taskmgr update), I believe) is zero. Thereafter it increases by about 200 with each new tab. And with one tab, the associated conhost.exe is at PFDelta=0 and with the opening of more tabs, each new conhost.exe (and the original one) are at about PFDelta=70. All the TCC's remain at CPU=0 and PFDelta=0.
 

rconn

Administrator
Staff member
May 14, 2008
10,103
85
#4
I don't see any CPU usage, but I noticed that with one tab open, TCMD's "Page Fault Delta" (page faults per second (taskmgr update), I believe) is zero. Thereafter it increases by about 200 with each new tab. And with one tab, the associated conhost.exe is at PFDelta=0 and with the opening of more tabs, each new conhost.exe (and the original one) are at about PFDelta=70. All the TCC's remain at CPU=0 and PFDelta=0.
You need more RAM.
 
#6
I have 1200 MB free ... almost never go below 1000 MB free. Other apps show PFDelta=0 when they're idling (except for explorer which, idling, shows PFDelta=1).
And those numbers are the same on another machine ( 3GB RAM instead of 2GB ) with 2300MB free. I suspect the PFs have to do with how TCMD watches the consoles and that Windows may be continually paging out stuff it doesn't think valuable (contents of hidden console screen buffers?).

As for CPU usage, TCMD and TCC seem, here, to use ZERO when they're idling. This display (TCMD and 4 tabbed TCCs, all idling) hasn't changed in over 10 minutes).
Code:
Running:        21.28 min
Total CPU:      1.6848108 sec
Total CPU:      0.2340015 sec
Total CPU:      0.2184014 sec
Total CPU:      0.1716011 sec
Total CPU:      0.2808018 sec
 
Running:        22.28 min
Total CPU:      1.6848108 sec
Total CPU:      0.2340015 sec
Total CPU:      0.2184014 sec
Total CPU:      0.1716011 sec
Total CPU:      0.2808018 sec
 
Running:        23.28 min
Total CPU:      1.6848108 sec
Total CPU:      0.2340015 sec
Total CPU:      0.2184014 sec
Total CPU:      0.1716011 sec
Total CPU:      0.2808018 sec
 
Running:        24.28 min
Total CPU:      1.6848108 sec
Total CPU:      0.2340015 sec
Total CPU:      0.2184014 sec
Total CPU:      0.1716011 sec
Total CPU:      0.2808018 sec
 
Running:        25.28 min
Total CPU:      1.6848108 sec
Total CPU:      0.2340015 sec
Total CPU:      0.2184014 sec
Total CPU:      0.1716011 sec
Total CPU:      0.2808018 sec
 
Running:        26.30 min
Total CPU:      1.6848108 sec
Total CPU:      0.2340015 sec
Total CPU:      0.2184014 sec
Total CPU:      0.1716011 sec
Total CPU:      0.2808018 sec
 
#7
Helllo Vince,

with which tool are you generating these statistics? Interesting!
 
#8
Helllo Vince,

with which tool are you generating these statistics? Interesting!
Hi, Frank.

I used PSTAT from my SYSUTILS plugin. I ran the command below in a TCC not in TCMD. The 5 PIDs are those of TCMD and its four tabbed TCCs.
Code:
v:\> do forever ( pstat 2008 /F RmT & pstat 908 /F T & pstat 1556 /F T & pstat 508 /F T & pstat 1256 /F T & delay 60 & echo. )
 
#9
OK, thank you. Of course I know your plugin, but I think I'll have to get more familiar with PSTAT :)
 
Jul 13, 2009
44
0
#11
It's unlikely they're doing anything. It's more likely that you have another app that's injecting something into TCC.EXE.
Would that happen -- another app 'injecting' something into TCC.EXE w/o my setting it up? As far as I know, I am doing nothing of the sort...
Here's a snapshot from TaskManager, immediately after starting TakeCommand:
 
Jul 13, 2009
44
0
#13
And those numbers are the same on another machine ( 3GB RAM instead of 2GB ) with 2300MB free. I suspect the PFs have to do with how TCMD watches the consoles and that Windows may be continually paging out stuff it doesn't think valuable (contents of hidden console screen buffers?).

As for CPU usage, TCMD and TCC seem, here, to use ZERO when they're idling. This display (TCMD and 4 tabbed TCCs, all idling) hasn't changed in over 10 minutes).
Code:
Running:        21.28 min
Total CPU:      1.6848108 sec
Total CPU:      0.2340015 sec
Total CPU:      0.2184014 sec
Total CPU:      0.1716011 sec
Total CPU:      0.2808018 sec
 
Running:        22.28 min
Total CPU:      1.6848108 sec
Total CPU:      0.2340015 sec
Total CPU:      0.2184014 sec
Total CPU:      0.1716011 sec
Total CPU:      0.2808018 sec
 
Running:        23.28 min
Total CPU:      1.6848108 sec
Total CPU:      0.2340015 sec
Total CPU:      0.2184014 sec
Total CPU:      0.1716011 sec
Total CPU:      0.2808018 sec
 
Running:        24.28 min
Total CPU:      1.6848108 sec
Total CPU:      0.2340015 sec
Total CPU:      0.2184014 sec
Total CPU:      0.1716011 sec
Total CPU:      0.2808018 sec
 
Running:        25.28 min
Total CPU:      1.6848108 sec
Total CPU:      0.2340015 sec
Total CPU:      0.2184014 sec
Total CPU:      0.1716011 sec
Total CPU:      0.2808018 sec
 
Running:        26.30 min
Total CPU:      1.6848108 sec
Total CPU:      0.2340015 sec
Total CPU:      0.2184014 sec
Total CPU:      0.1716011 sec
Total CPU:      0.2808018 sec
Here are my results from pstat (the first item is TCMD, the next two are TCCs):
C:\Temp] 8:38:01>ver
TCC 15.01.40 x64 Windows 7 [Version 6.1.7601]
do forever ( pstat 12552 /F RmT & pstat 1660 /F T & pstat 7276 /F T & delay
60 & echo. )
Running: 2.55 min
Total CPU: 2.8860186 sec
Total CPU: 12.8544824 sec
Total CPU: 13.4004858 sec

Running: 3.55 min
Total CPU: 3.3228213 sec
Total CPU: 18.0337162 sec
Total CPU: 18.0493154 sec

Running: 4.55 min
Total CPU: 3.6660234 sec
Total CPU: 23.0569480 sec
Total CPU: 22.9789472 sec

Running: 5.55 min
Total CPU: 3.8220245 sec
Total CPU: 27.9553800 sec
Total CPU: 28.1893800 sec

Running: 6.55 min
Total CPU: 3.9000250 sec
Total CPU: 32.6354088 sec
Total CPU: 32.3234068 sec

Running: 7.55 min
Total CPU: 3.9468253 sec
Total CPU: 36.3638328 sec
Total CPU: 36.0986324 sec

Running: 8.55 min
Total CPU: 4.4460286 sec
Total CPU: 39.9206544 sec
Total CPU: 39.9518544 sec

Running: 9.55 min
Total CPU: 5.0076322 sec
Total CPU: 41.3246652 sec
Total CPU: 41.3870644 sec