In message , Rene Lamontagne
writes:
On 03/17/2019 6:06 PM, VanguardLH wrote:
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.
Yes, for me I notice it has gone to 25% (of an apparently 4-core
processor), and doesn't come back down (even if I close the GUI).
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.
I've never even heard of any of those other than Process Lasso, and am
not running that (-:.
Do you run any process (manually, startup, scheduled) that results
in
renaming or deleting entire folders? Doing such is expensive to
Nothing I can think of.
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
I don't think I'm doing anything like that! The main prog.s I am
normally running are an old Firefox and a new Chrome, my news/email
client, Notepad+, Everything, Brother's Keeper - genealogy, a biggish
database handler but not actually doing anything most of the time), and
the odd tiddler like AllChars, noisy keyboard, and the like. Nothing big
- I'm no power user! About the only CPU-intensive thing I ever run is
very occasional video conversion/editing, but I know when I'm doing
that, and _expect_ the fan to take off.
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.
I'll look at the disk light if it ever does it again. (It's now been
running thirtysomething hours in "placid" mode.)
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.
It's set to 0 at the moment. When I've looked at task manager when it
goes to 25%, it isn't all in one core, though it's not symmetrical - two
of them seem busier than the other two.
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)?
NTFS. I did on another machine try using FAT, but I found Everything
worked a lot less well with it: I don't remember in what way, but it was
and has been the only thing that's ever made me use NTFS. (I've used
NTFS when a machine has come set up with it. I can't remember how I came
to be using FAT on that machine - maybe I was setting up a new partition
or something.)
Just did another test on mine watching task manager all the while,
Opened Search everything and typed in one word, usage was at 0% and
jumped to 2% for 2 or 3 seconds then returned to 0%, CPU dropped back
to 1.61 GBs. which is about half speed,
and idled there for about 10 minutes as I watched. memoru usage was
steady at 2.2 GB
So in my case at least the program is running normal.
Rene
Thanks. Yes, I've just tried the same - as I typed characters into the
search box, Everything.exe in Task Manager went to 03 for one Task
manager refresh interval (I seem to have Task Manager set to Update
Speed - Normal, which seems to be about once a second), then drop back
to 00, for each character I typed.
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf
"I hate the guys that criticize the enterprise of other guys whose enterprise
has made them rise above the guys who criticize!" (W9BRD, former editor of
"How's DX?" column in "QST")