Forum Discussion
OneDrive Client, Files on Demand and Syncing large libraries
Any new updates on this topic? I have a Document Library with about 115,000 files in it and our users are having problems with the OneDrive sync getting stuck on "processing changes". Sometimes I can do a OneDrive reset, but other times it doesn't work. We're well under the 300k file limit.
Nothing major that will simply "solve" the problem unfortunately.
Couple questions:
What Client version are your users running?
Does the library contain folders with broken inheritance?
How many users are syncing the library simultaneously?
Does the library have a high rate of change? (i.e. lots of files being modified in many different folders) or is it a lot of old static content?
The latest Production ring client: 20.134.0705.0008
No broken inheritance.
Around 5-10 users syncing at the same time.
Yes, high rate of change.
I gave myself permissions and started syncing the library and I'm having similar issues. So I don't think its machine related. I can't even reset OneDrive now, it gives an error that is couldn't shut down OneDrive.
Its likely the rate of change that's causing you the most problems. Every time something changes (especially in a file copy scenario), OneDrive has to re-scan everything that's on disk to ensure that it hasn't lost a file somewhere (i.e. "Was this thing renamed? or was it moved? or both?"). When multiple machines are moving a lot around, it exponentially increases the local demand on each individual machine. The only way to alleviate this is to break up the content across multiple libraries. Do all 100,000+ files need to all be in the same library? do they have to all be brought down locally? if you are lucky enough to answer no to both of those questions, the solution is simple: break up the content into smaller libraries and make stale data online-only (disable sync through in the library settings).
Unfortunately, this isn't exactly OneDrive's fault, Windows still has no mechanism where an app could simply subscribe to a subsystem and say "tell me anytime something changes on disk, including all the context". That leaves it with no other alternative than to literally go searching the disk every time anything updates to make sure it hasn't lost anything... but if it gets overwhelmed with too many changes it simply cant keep up.
Ok thanks. That was the direction I was heading by either choosing folders/files not to sync or archiving/moving files into a different Document Library to cut down on the files that sync.
