Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That's a mis-framing of the situation.

The issue isn't so much as the client is failing - but that it wasn't designed to handle their edge-case - and trying to sync 700,000+ items, or 700GB worth of files to your desktop is definitely at the edges.

Other desktop sync clients (e.g. Box.net or Dropbox) exhibit similar performance characteristics - e.g. Dropbox advertise a limit of around 300,000 files (https://www.dropbox.com/help/space/file-storage-limit). So this isn't something specific to us.

For us, I know there isn't a hard limit per se, but there are memory limitations, due to this being a 32-bit binary. So things like the user's environment, and the length of certain fields could also play a factor.

However, it is something that I know several smart people are chipping away at steadily - in fact, there's a new "Backup and Sync client" we announced a month or so ago, which is launching any day now. It's basically Drive Sync Client 2.0.



seems like if there's a limit to the number of files the client can handle, the client should warn you as you're approaching that limit, and ideally block you from adding too many.

If the client allows you do do something, and you do it, and it causes the client to break, that is 100% a "failure"




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: