View Single Post
  #48  
Old March 18th 19, 04:51 AM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default is "Everything" doing some mining?

J. P. Gilliver (John) wrote:
In message , Paul
writes:
[]
I wonder. If you had a million files in an IE cache,
would the dates on the files change when you use IE ?

I would want to understand just how many files were
on this machine, for a starter. To see if there is
"any potential way for scaling to account for it".

Like, if there were 10 million files, you would
expect the indexing (if and when done) to take
longer than an average install/use of 0.5 million files.

[]
Everything's search GUI tells you how many matches there are to the
string you've typed in. With no string, which I think means it's showing
all files (and folders), the figure showing is "211,629 objects". If I
enter C:, it says 158,032; D:, 53,598. [So there's a lot of _garbage_ on
C:!) It's a fairly static number - as I watch it now, the last three
digits are varying between 630 and 631, suggesting the OS is not
creating and destroying many files as it idles. Now (after a minute or
three) it's changing between 631 and 632. Just out of curiosity, I'll
close Chrome ... odd, that (with JS enabled and about ten tabs open) was
the only thing I thought would be doing much. OK, I'll close Firefox ...
also no change. Did go up gradually to 211,625 - now back at 211,619.


So that's not it.

It's a small machine, and scaling isn't the problem.

*******

So something is going into a loop, and our last choice is ProcMon.
Even if you don't know how to use it, just use the trace windows
scroll bar and see if the Everything.exe process is accessing files
and so on. You don't need to mess with filters. Just close the
filter window, and let it capture a trace, then scroll down
and see if there are readfile, writefile, createfile, or the
like, associated with everything.exe. Use the "X" box in the
upper corner, to stop it. This way, you don't have to learn
anything.

https://docs.microsoft.com/en-us/sys...nloads/procmon

If the trace is quiet, and *no* events with the process name
of "everything.exe" are being recorded, it means everything.exe
is in a memory-intensive loop or a cpu-core intensive loop,
and isn't even going near the file system. And this could mean
that somehow (and quite quite unlikely), one of the algorithms
it uses has gone nuts. Perhaps it's a problem with the USN
journal, or, some *other* program is tiddling the date
on a file, over and over and over again. And everything.exe,
being a good boy, is reading the USN journal in response.
Note that this sort of loop *also* happens with Windows Search
indexer, but usually the loop-age is at the 1Hz rate, and not
a good solid infinite-loop. Microsoft specifically put in
rate-limiting in their design, so people would not notice
their screw-ups and corner cases.

Paul
Ads