Post by PaulPost by Rene LamontagnePost by J. P. Gilliver (John)[]
Post by Rene Lamontagne I saw the 0% the first time you said it! But, presumably, for them
to appear in Task Manager _at all_, they (all three of them) must
be using _some_ cycles - even if it's one a fortnight. Or some
memory. If they weren't, they wouldn't be listed. (Task Manager
rounds to nearest %, and I think K, so will show 0.)
There are dozens of items listed in task manager that are *Not*
using cyles at all, so your presumptions would be incorrect.
Rene
{How did they get into}/{Why are they still in} the list of items in
Task Manager, then? (Not just the Macrium ones, but all the other
"dozens".)
Don't Know, Someone with more knowledge of task manager might know.
Rene
When something is railed in Task Manager, you have the
option of studying it in Process Explorer (sysinternals.com).
https://s14.postimg.org/6ba7eypc1/Rpc_Ss_busy_loop.gif
A "svchost" is, as the name implies, a "host for services".
A service "takes requests" and "delivers results". Multiple
services can live inside one SVCHOST.
In older Windows OSes, like WinXP, one of the SVCHOSTs had
15 services in it, and they were all "network oriented".
On Windows 10, by comparison, for reasons unknown, Microsoft
has implemented a "one service one SVCHOST" policy, but, it
didn't do it for everything. The result is, the Task Manager
list in Windows 10 is *huge*, but it's huge for two reasons.
There are more services. The services have been given their
own SVCHOST to hide it.
A well-written service, doesn't use any cycles unless you
"talk to it". Services should not be like proper "processes"
and should be lighter in weight, and also lighter in
intent. They're not like a copy of Excel or Word, and don't
use up nearly the same amount of resources. They don't
put a window on the screen AFAIK.
Think for a moment, of a hypothetical "spooler service".
The user wants to print. The printer isn't ready. What
better way to handle it, then have a queue where the
print can be saved, and dribbled out as the printer
is ready for it. I "call" the spooler service with my
print file, and between the spooler service and some printer
service, they dribble out stuff until it is done. As a program,
I can disconnect from the spooler service, while the spooler
service handles the whole print job for me. It means my program
doesn't "jam" until the entire document is printed. The
program doing the printing, is responsive almost immediately
after the print operation happens. And it's all because a
spooler service could be designed to offload individual
programs, and prevent them from "jamming up".
In the picture above, RpcSs service appears to be
doing garbage collection (recovery of unused RAM) for
the desktop display process (the entire desktop is
some kind of program). It had something to do with
the thing that MSEdge was doing, and MSEdge needed a lot
of RAM to do it, then later, MSEdge gave the RAM back.
That RpcSs service for some reason, seemed to be making
RAM freeing calls for about 20 seconds continuously. Which
smacks of bad design. It's like your mom has left for
a three week vacation, and you decide to do 50 loads of
wash an hour before she arrives back from vacation. And
it's too little too late. That garbage collection should
have been done in much smaller time segments. Not left
until the last minute.
In the old days with Unix, you had daemons. The "inetd"
process was a daemon for dispatching things. One of the
things reporting to it was "telnetd", a telnet support
daemon. If the user telnetted remotely to the
computer with an 80x24 terminal, inetd would see the
activity on some control port, and would wake telnetd up
to respond to the login attempt and session. The concept
of services has existed with other names for it, for
some time.
For me, the worst part of the Windows scheme, is it's
so hard to use debugging tools to compare "inside" and
"outside" activities. Some of the tools I use would tell
me "svchost 1156 is doing something", but then I couldn't
peer inside to see any details. And that sucks. I like it
when each service has a unique name (i.e. viewable at the
Task Manager level), and just the name alone hints at what
job it's doing, and why it might be railed.
Paul
all it does.
It seems to work (most of the time) so I just let it do what it does.
I just did a backup using Macrium and this is some info I gathered.
The CPU speed varied between 2.6 GHz to 3.06 GHz.
CPU load ran from 11% to 16.5%.
6 cores seemed to be the most active, 2 cores were not used as much.
just as an aside I have 168 items listed under processes.