I did notice a significant overhead when opening file handles on my system and am trying to confirm if Everything is responsible for it or not.
Unfortunately that overhead is a bit inconsistent so I would like to confirm some assumptions and identify how to best configure Everything in case the overhead is indeed coming from there.
The issue:
It takes on average 3ms to open file handles, the profiler flame graph attached shows that most of that time is spent in the FileManager Filter module, in KeSaveStateForHibernate. Note that hibernation was entirely disabled on the affected computer.
- image.png (126.75 KiB) Viewed 1002 times
I have a similarly configured machine that doesn't appear to be affected by this issue, that machine does not have Everything installed.
Figuring out if Everything is causing this:
I tried the following (not all at once and not necessarily in order)
- Disabling "Monitor Changes" for the volume on which the data lives (NTFS volume)
- Setting "!D:/MyFolder" in "Include only" for the NTFS volume in the hope that it won't monitor that folder
- Killing everything
- Killing the everything service
Doing this gives me inconsistent results, it will appear like the issue is gone but then the issue will reappear later on.
Some notes:
- The file is opened as read-only so I don't expect Everything to monitor the file handle being created but I don't know for sure
- LastFileAccess was disabled on the machine (this is a windows setting that is known to negatively impact performance upon opening files)
What is the best way to guarantee for sure that Everything isn't interfering with File IO?
Is it possible to configure Everything to monitor changes in a volume except for some folders? I still want those folders in the index but reindexed nightly.
Thanks in advance