When examining Everything's performance via Sysinternals procmon -- I've noticed that a huge chunk of the CPU time was "wasted" on calling OutputDebugStringW WinAPI, which is invoked by DllInstall WinAPI.
So, I wander if it's Everything or Google Drive to blame?
Is there a way to avoid this, in your opinion?
I'm attaching a screenshot of Sysinternals procmon "Stack Summary" for that session:
![Image](https://i.imgur.com/vWjoeDe.jpeg)
As you can see in the screenshot -- it seems that Google Drive is the one to blame for the DllInstall calls. But, maybe this entire "code path" can be avoided in some way by Everything.