View Single Post
  #3  
Old July 17th 18, 01:16 PM posted to alt.windows7.general
J. P. Gilliver (John)[_4_]
external usenet poster
 
Posts: 2,679
Default What's "Everything" doing?

In message , Paul
writes:
[]
Anything that "indexes" automatically, can get
into a loop.

[]
Or, strictly, if you have _two_ such indexing utilities running (e. g.
Everything and something that's intrinsic to Windows). Understood.

What this means is, exceptions have to be added somewhere,
to stop such behavior.


I _suspect_ that's not possible as I _suspect_ it's triggered by
different things, and I'd be playing whack-a-mole (and building an
unwieldy exceptions table/list/whatever).
[]
You might also set up Everything.exe to not use the USN
journal, and only index the disks once a day or something.
But this isn't ideal either, as your indexes won't be
up-to-date when you need them.


Indeed.

Anyway, that's an illustration. You could use Process Monitor,
the ReadFile and WriteFile events, to note which
programs are playing table tennis with which files. And
concoct a theory covering the behavior.


Life's too short (-:
[]
I'll just keep an eye on it. I wouldn't even worry about it if I wasn't
worried about overheating after my last computer; on this one, the
internal fan seems well-controlled, and my usual indication that
something's using more CPU is when I hear the fan step up. (I don't even
know whether it's CPU-load-triggered or temperature-triggered, though
I'd guess the latter.)

FWIW, Everything has now been running for several hours since I
restarted it, and is still in the 00 range.
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

"If even one person" arguments allow the perfect to become the enemy of the
good, and thus they tend to cause more harm than good.
- Jimmy Akins quoted by Scott Adams, 2015-5-5
Ads