We’re Still Here to Help (Even Over the Holidays!) - find out more here.
Forum Discussion
Solved
With a 300k file limit does Dropbox really provide business solutions?
For many many years, I've been a Dropbox Pro member. During this time, they decided at some point, that 300,000 files is the maximum they will support. Now, I know what you are thinking. The ar...
I did not accept this as a solution (now fixed). It doesn't solve anything and is factually incorrect. At the time of your reply and this post, there is a baked in hard-limit in Dropbox that makes it unusable - and your support team refused to provide support to anyone with over 300K files. Nothing in your response you marked as the "answer" addresses this in any way shape or form. Wishing you had the answer isn't the same as providing one.
The right answer was moving to Google Drive and getting an actual business grade cloud based file sync solution in place.
Afaik it is a 2 part problem.
My theory
On the PC side, they created a 32bit application which means a hard memory limit of 4GB. And they built it in such a way it had to retain every file in memory, instead of just a reference to the file. So after 300k files they will hit some kind of internal memory limit. And somehow they loop it through system processes, which can cause a BSOD.
The bigger problem is their backend is a hot mess. I get server and 404 errors all the time - even just doing basic operations like restoring files.
I think they made some poor architectural decisions that can't be solved without impacting their full user base. And that's why services like Google Drive - which no longer follow those old architecture patterns, aren't having these issues.
It's important to remember their bread and butter is users paying monthly with only 50 files - anyone seriously using it they don't want and can't afford to keep on their fractured platform. Imho of course
My theory
On the PC side, they created a 32bit application which means a hard memory limit of 4GB. And they built it in such a way it had to retain every file in memory, instead of just a reference to the file. So after 300k files they will hit some kind of internal memory limit. And somehow they loop it through system processes, which can cause a BSOD.
The bigger problem is their backend is a hot mess. I get server and 404 errors all the time - even just doing basic operations like restoring files.
I think they made some poor architectural decisions that can't be solved without impacting their full user base. And that's why services like Google Drive - which no longer follow those old architecture patterns, aren't having these issues.
It's important to remember their bread and butter is users paying monthly with only 50 files - anyone seriously using it they don't want and can't afford to keep on their fractured platform. Imho of course
This all makes sense. But it's hard to believe that something else hasn't changed recently. I didn't have these sync issues two months again and virutally nothing has changed on my end. The new versions of the software don't even lead to a connection/sync. Only 51.4.66 installs correctly which leads me to believe there are further regulatory changes embedded in the architecture. Further, the online platform shows my PC synced and operating on that same 51.4.66 version. Further suggestion that they've made recent changes. Of course, the auto update then renders the sync useless and no one at DB has actually explained the changes despite me asking over and over.
