Its almost for sure going to cause Dropbox to crash and restart during this process (it happens quite frequently), Someone else adds a bunch of files on another machine However if you don't let Dropbox finish before doing something else (like adding more files or using the computer for other tasks) This causes Dropbox to start indexing them all at once causing the system to slow to a crawl On a computer with too many files (1-2+m)

If you add 'too much stuff' (copying 200,000 files of small size in one go, coders know what I'm talking about)ĭo it 'too fast' (changing access permissions on 1.5 million files located within Dropbox in one go in less than 5 minutes) When you add stuff to your Dropbox, Dropbox has to index it so it can know what to do with it. So our business Dropbox is more than 9 million files strong, I've noticed REALISTICALLY any machine handling over 2 million will just enter an indexing loop at some point from which it will never recover, after its happened 5 times in the last week I was pissed enough to that I decided I was going to find out why this is happening, I know I'm pushing the limits but we've had machines with 2.5m files running fine for years, why some work fine and some don't was a mystery, one I was determined to find out. Ok so I've used Dropbox for almost as long as its existed and recently due to frustration with the never finishing indexing bug I was forced to find out why this kept happening so I could prevent it.īear with me on this long post but trust me its worth it, what I found was mind blowing and game changing.

Palia instal the new for windows