-
Notifications
You must be signed in to change notification settings - Fork 813
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This client is still a headache when your users have thousands of files. #6501
Comments
The Mac OS implementation is going to change in favor of a FileProvider approach, which changes things radically but unfortunately that API is available on MacOS only. On the good side, it also seems like much has been done to ease rough edges out. One step in that direction would be having a right-click mouse action (available in virtual drive mode too) on folders and be able to remove that folder (and its contents) from sync, leaving it grayed (plus an “add” right-click action available) instead of having to do that in a config panel; that alone would drastically reduce the problems. Automate that using a lazy approach and you’re done… |
Well I wish, I still defend this kind of products, but when you face so many problems you think about going back to google, you end up investing more money in infrastructure, storage to guarantee a good service. |
This is related to #4424 |
Duplicate of #4424 |
Unfortunately I have to synchronize thousands of files and hundreds of folders despite having a great architecture, it is almost impossible to keep customers happy with this client.
Why does it just work at least like the android version?
Why does the user have to wait hours for his files to show up (3 hours for 380,000 documents)?
I have gone out to buy webdav (webdrive) clients (I have to do it because microsoft little by little wants to kill the webadav service)...so the users don't have to wait. please consider not doing that sync just show the files and that's it like Google Drive does. and don't come to tell me that google is google, I have tried nextcloud in clusters with redis SDD S3 and how much stuff there is, but I see that this client is simply supremely slow.
The text was updated successfully, but these errors were encountered: