FYI: opened-by: uses lots of CPU

[NotNull]

Probably a Windows shortcoming and not Everythings fault, but for example opened-by:everything64.exe utilizes 37-50% of available CPU here. Admitted: CPU is outdated and underpowered, but that is still way more than I expected.
For reference: perfmon.exe (Resource Monitor) uses 5% CPU for the same (live) results.

Just a FYI.


(Win 10 21H2; Everything 1.5.0.1313a x64)

[void]

Thanks for the issue report NotNull,

Everything uses PssCaptureSnapshot.

This API is quite slow.
There is a lot involved with taking a snapshot of all opened handles in the system.

I have put on my TODO list to add an ini setting to control the polling rate.
The current is 1 second.

I was seeing 1-5% CPU usage on my Windows 10 test machine.

[void]

Everything 1.5.0.1315a adds a poll_opened_files_rate ini setting.


To decrease the rate in which Everything gathers opened files:

• In Everything, type in the following search and press ENTER:
  /poll_opened_files_rate=3000
• where 3000 is the number of milliseconds to wait before updating the internal list of opened files.

The default is: /poll_opened_files_rate=1000

[NotNull]

Thank you.

/poll_opened_files_rate=3000 is the sweetspot for this system. It gives enough time to take the snapshot and process the information before the next polling takes pace.

No need to change the defaults though. As said this is a really slow system (on purpose). My 2 year old i5 CPU is 25 times faster ...
(although I suspect the real bottleneck here is memory)