Why TC use 0.11% cpu constant when not inactive?

[Hurdet]

Why TC use 0.11% cpu also when it does not do anything and is minimized?
Do it is possible to reduce to 0%?

[gdpr deleted 6]

Do you really mean zero point eleven percent, which is about the 1/1000th part of a thing? Why would you ever worry about such an insignificant amount like this?

Or is that a typo in your post and you actually meant 11%?

[Hurdet]

i mean 0,11% constant.
If it is possible I prefer not to drip the faucets.

[gdpr deleted 6]

Well, i guess if 0.11% is that important to you, you will have to troubleshoot your particular situation. For me personally, 0.11% is not worth putting any thought and spending any significant time on it.

Only so much: Check TC's configuration in detail for any setting or combinations of settings that could cause this minor load. Experiment with the configuration settings and observe whether and how the CPU load would change. Monitor TC's CPU load over time and in correlation to what you do within TC and also in correlation to what other programs (including services) do and what you do on the desktop elsewhere. (Remember, that even when you interact with one program it might become necessary for another program to do 'something', like for example reacting to some system event it subscribed to, redrawing parts of its UI -- although not when minimized, etc...). Perhaps you can learn from the collected information under which circumstances TC's CPU load changes for better or worse when it is running on your particular system configuration. Good luck!

[MVV]

First of all, you should try disabling auto-refresh on file system changes.

Also starting TC with clean INI (TOTALCMD.exe /i=new.ini) may help to know default load level.

BTW my TC eats now 0.07% when it has no focus.

[Hurdet]

First of all, you should try disabling auto-refresh on file system changes.
BTW my TC eats now 0.07% when it has no focus.

now it remain 0.05% constant.

[Hacker]

Hurdet,
0.01% here.

Roman

[ghisler(Author)]

Something must be keeping it busy, e.g. a constant flow of WM_DEVICECHANGE messages or file system updates. Are you perhaps doing a background download or so?

Btw, which tool do you use to see the percentage in 1/100 of a percent? Even on Windows 10 the task manager only shows 1/10 of a percent here, and it's always 0 for TC while in the background...

[Hurdet]

I not have background download and TC is minimized and inactive.
I use ProcessHacker to see cpu percent.

[gdpr deleted 6]

Btw, which tool do you use to see the percentage in 1/100 of a percent? Even on Windows 10 the task manager only shows 1/10 of a percent here, and it's always 0 for TC while in the background...

FYI: The Resource Monitor (which can be invoked from the task manager) shows an average CPU load with a resolution of 1/100% (averaged over the last 60 seconds). I am not sure whether the resource monitor has been optimized away in Windows 10, though. Process Hacker seem to show the momentous CPU load with 1/100% resolution, i guess (but i might be wrong, i am not a user of PH)

[TW]

process hacker swaps between 0.01 and 0.02 CPU even on my crappy i5-3520m laptop.

FYI: The Resource Monitor (which can be invoked from the task manager) also shows an average CPU load with a resolution of 1/100% (averaged over the last 60 seconds).

yes, that one shows even 0.00 here.

if you want 0.00000000% do suspend it.

[ghisler(Author)]

Ah, thanks, I missed that one. It shows 0 for TC for current CPU, and 0.01 on average.

[Hacker]

Christian,

which tool do you use to see the percentage in 1/100 of a percent?

Process Explorer.

Roman

[Hurdet]

These are the thread that occupy the cpu:

Code: Select all

0.6%

0, ntdll.dll!ZwWaitForMultipleObjects+0xa
1, KernelBase.dll!WaitForMultipleObjectsEx+0xef
2, user32.dll!MsgWaitForMultipleObjects+0x1e9
3, user32.dll!MsgWaitForMultipleObjects+0x6b
4, TOTALCMD64.EXE+0x419c7f
5, 0x1c0fab0
6, TOTALCMD64.EXE+0x1a530
7, 0x1c0fab0
8, 0x7ff5ffff5000
9, 0xff
10, 0x1c0fc40

0.3%
0, ntdll.dll!ZwWaitForMultipleObjects+0xa
1, KernelBase.dll!WaitForMultipleObjectsEx+0xef
2, user32.dll!MsgWaitForMultipleObjects+0x1e9
3, user32.dll!MsgWaitForMultipleObjects+0x6b
4, TOTALCMD64.EXE+0x300a96
5, 0xc2440
6, TOTALCMD64.EXE+0x15570
7, 0xc47fdc0

[Phred]

Not even zero point one one[sic] % here.
Dark zero zero.

Your faucet may not leak, Hurdet, but I bet your pipes do, somewhere..
Out.