An error occurred while saving the commentRichard commented
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.
1 vote0 comments · OneDrive on Windows » Desktop (Sync, Files On-Demand) · Flag idea as inappropriate… · Admin →