View Single Post
  #8  
Old July 18th 18, 12:42 AM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default What's "Everything" doing?

J. P. Gilliver (John) wrote:
In message , David E. Ross
writes:
On 7/17/2018 3:38 AM, J. P. Gilliver (John) wrote:
I just found Everything using most of one of my cores, after leaving the
machine unattended - but on - for some hours. It showed in task manager
as using 2x% of CPU (Task Manager thinks I have four cores), and when I
shut it down (via the tray icon, not from Task Manager), CPUsage went
back to idle.

I've just reopened Everything (once I have opened it, I normally leave
it open, as it's so useful), and (after initial peak) it's sitting there
down at near enough zero CPU usage again.

I've noticed this behaviour more than once recently. Anyone know what
it's doing? FWIW, it's "Version 1.4.1.895 (x86)".

(Hour or two later: it's still down in the 00 usage.)


Try the following:

1. Launch Everything.

2. Select [Tools Options] from its menu bar.

3. On the left side of the Everything Options window, select General.

4. On the General pane, uncheck all checkboxes except for "Show Search
Everything folder context menu item" and "EFU file association".

5. Select the OK button.

That might be a cure, but not an explanation as to why it was - when I
came to the computer after hours away - suddenly busy.

FWIW, on that window I currently have (ticks): 11001110101. And it's
using 00 CPU.

To whoever suggested indexing: possible, but when I start it up from not
running, it seems to do whatever it does - I'm assuming something like
indexing, because its list isn't populated until it's finished - in well
under a minute (190,484 objects, it says at the moment). And I think
it's indexing continuously, because if I create (e. g. download) a new
file, I can see it in the Everything list immediately.


Everything.exe doesn't do content indexing.

At least the versions I've tried didn't.

Originally, it would read the $MFT for file names.
This approach can be lightning fast, from a theory point
of view.

But this doesn't give size or date information. To gather
those requires consulting directory filenums or the like,
one at a time. This required disk head movement.

If Everything does a "wake-up" scan, then it will take
some time to visit the directories and collect the
information.

In the case of "incremental" file info, the USN journal
logs the fact a new file was created, or an old file
was deleted. This allows Everything.exe to add or
delete entries in its index. Everything.exe would still have
to visit the directory, to get size and date, when
files are added.

All of these procedures should be light-years faster
than the content indexing that Windows Search does.

Even finding Everything in a "loop" doesn't make
a lot of sense. It implies Everything has "tangled"
with MsMpEng Windows Defender. Defender can easily
do Ninja stuff, to rail any ordinary process. In
addition, Windows Defender can "jam" programs on
I/O, and they'll stay jammed unless the program
uses a timer to detect such a failure. Most programs
assume, that one way or another, an I/O call will resolve
in 15 seconds, no matter how bad the outcome ("delayed
write failure"). The additional failure modes that
AV programs cause, are not normally considered by
application programmers.

Paul
Ads