View Single Post
  #41  
Old March 18th 19, 12:06 AM posted to alt.windows7.general
VanguardLH[_2_]
external usenet poster
 
Posts: 10,881
Default is "Everything" doing some mining?

J. P. Gilliver (John) wrote:

Has anyone else had the odd behaviour - does an index when you start it
(I think), then settles down to idle, then does something else that
takes longer than the initial index (or whatever) activity? Or is it
just me?


Of the 8 respondents, so far, none have noted their own encounter with
the sporadic jump to 25% CPU usage just for the everything.exe process.
Could be just you. Could be there is a jump but it is so short-lived
that users wouldn't notice it versus for you where it sticks at the 25%
CPU usage for long enough for you to notice.

Are you using anything regarding the CPU, like affinity, on how to run
the program? Or some CPU dispatcher or priority enhancer (e.g., Process
Tamer, Bill2's Process Manager, Prio, Process Lasso) instead of using
just the one in Windows? As I recall, some of those could also define
an core affinity for some processes or how many cores a process can use.

Do you run any process (manually, startup, scheduled) that results in
renaming or deleting entire folders? Doing such is expensive to
Everything in that the entire folder and all its files, especially if
many, have to update its index database. Perhaps you are dumping tons
of files into, say, the %temp% folder and then run a cleanup tool either
automatically due to thresholds (number of files, aggregate size),
manually, or scheduled. When there are huge changes to the file system,
Everything has a lot of work to do. It's not just folder deletes that
could impact Everything. For example, if you run SQL Server Management
Studio (SSMS) which massively interacts with its drive by frequently
writing & deleting lots of session data, Everything has to keep catching
up. When Everything's CPU usage jumps up, you might want to look at
your disk activity to see what other processes might be doing lots of
changes in the file system.

Everything uses multiple threads to complete much of its work in
parallel, and that could impact CPU usage. You can edit the
everything.ini file to change the max_threads. I think max_threads=0
means to disable throttling of thread count. You could max_threads=x,
where x is the number of logical CPUs (cores) minus 1, or to a lesser
number to generate less threads for Everything. With less threads,
updating will take longer but as less CPU usage.

https://www.voidtools.com/support/everything/ini/

I don't recall you mentioning what file system you are using. Most of
us probably assumed you are using NTFS, but maybe you are using FAT.
Everything can use the Journaling in NTFS to detect when a file has
changed. In Everything for the NTFS config, is "Enable USN Journal"
enabled (assuming you are using NTFS for the file system)?
Ads