Control Everything CPU usage at startup?

[ccb]

TC v23 on Win10 Pro x64
When the computer starts up Everything starts running, taking >50% of the CPU.
It takes as much as >90% for significant bits of time.
This leaves the computer pretty much unusable...

s there a way to limit the CPU use by Everything?
I don't care if it takes longer to index the disk, I want to be able to use the computer immediately after I log in.
Thanks --

 

[rconn]

There is an option in the Everything Options dialog (General) "Start Everthing on system startup." If you have that option checked try disabling it.

 

[ccb]

That just delays the problem until I first want to use Everything - I start it up and it quickly heads for >90% of the CPU.
Seems like very rude behavior for just about any application or service...

 

[rconn]

I'm not aware of an Everything option to run slowly.

If you're running an elevated TCC session you could lower the Everything service priority.

 

[ccb]

I'm running Everything as a service, so it has nothing to do with a TCC session, elevated or otherwise.
If Everything is set to run at startup, TCC is nowhere in sight (unless the Everything service start up TCC for some reason).
Similarly, I can start the Everything UI w/o ever having run TCC.

 

[vefatica]

Have you visited the Everything forum? Perhaps you can find some tips there.

General - voidtools forum

 

[rconn]

I'm running Everything as a service, so it has nothing to do with a TCC session, elevated or otherwise.
If Everything is set to run at startup, TCC is nowhere in sight (unless the Everything service start up TCC for some reason).
Similarly, I can start the Everything UI w/o ever having run TCC.

Even if Everything is already running as a service, if you start TCC elevated, you can use the PRIORITY command to bump the Everything service's priority downwards.

 

[vefatica]

Did you see this one? GUI\Tools\Options\NTFS\<drive>\
Maximum size
Set the maximum size of the USN Journal in KB. If Everything is rebuilding the database after restarting Windows, try increasing this size to at least 32768 KB.
If the journal grows larger than this value it is truncated by removing the specified allocation delta from the beginning of the log.