Reduce OneDrive + Explorer unnecessarily high CPU usage on small file changes
Im using OneDrive on the latest Windows 10 v1703 with a free hotmail account.
My synced work folder contains ~ 22.000 smaller files in ~ 2.7 GB of disk usage.
The files are evenly distributed over the folder hierarchy, with no more than ~ 50 files per folder.
To start, all files are synced. (All green checkmarks on files and folders)
When I then update a small simple text file in a folder, say, nested 3 levels deep, OneDrive starts syncing that file, as it should.
However then it also seems to start checking of all "nearby" folders in the folder tree.
Windows Explorer keeps flashing the green checkmark of folders and repeatedly updates its view, unnecessarily.
This causes High CPU usage in both OneDrive and Explorer for every small file update.
So much CPU/battery is used that I have to turn off OneDrive syncing when working on my laptop on the battery.
While this fashing / updating is occuring in Explorer, it is nearly impossible rename files in Explorer.
When OneDrive updates, a partially renamed folder (while typing) is "accepted" as a full rename. Very annoying.
Fix the sync algorithm so that one (1) updated file does not cause a recheck of the entire folder tree.
And OneDrive should signal only the updated file changed to the opened Explorer,
and not make it a "flashing Christmas tree with green lights" for a a couple of seconds.
I'm told then DropBox and Google Drive do not have this issue...
We are now 3 years further.
I'm glad to say that the Explorer part of this issue has been fixed now; it stays relatively 'calm' after a small file update. (It still frustates renaming of a file just after it has been created in a OneDrive folder.)
OneDrive itself, however still uses way to much CPU on file small updates. Adding 1 file of size zero to a OneDrive subfolder still causes 12 seconds of full CPU usage on one core of my quick Core-i7 processor. So my cooling van spins up after every file update. My laptop battery drains quickly.
I now have ~ 30.0000 small files on that OneDrive and ~ 13.000 folder, with no more than 10 files per folder.
@OneDrive Developers: You can fix this with intelligent use of the FileSystemWatcher API of Windows. (System.IO.FileSystem.Watcher.dll). Please take a look at it. Thanks.