I have 12000 files in my Ubuntu One account. With the first computer that all the files were created on, there is no problem keeping it in sync between the web and shares. However, recently I added a new computer and started to sync it. Unfortunately, the way it processes the queues, I could never get is synced.
Whenever syncdaemon starts, it does a localscan, then server scan, and it queues up any changes that are needed. Unfortunately, it seems as though the content queue is the last thing to process. So it doesn't start downloading till last. Unfortunately, any interruption makes my client start all over again. This is problematic since this is a laptop. It was also a problem since my crappy router kept dropping the wifi connection. So far after days of syncing and restarts, I have only received 2000 of the 12000 files.
Note this also occurred with another laptop using a different account that I had shared lots of files with. The laptop would never process any changes since all of the metadata/content had to be queued and anything I did locally wouldn't get sent to the server right away.
The only way I could ever imagine it ever working is if I left it connected and on for many days without an interruption in connections. This is not an option.
Some suggestions:
* Reduce the size of the queues so that the entire process local/server/content can be processed in a short period
* Prioritize events that the user may trigger manually (creating a file etc) so that when I do something, it happens now.
* Prioritize events that come from the server.
* If a user event comes in, could effect queued events, handle it appropriately. For example, if a node deletion comes in, remove if from the queues.
I don't think this is going to change for Lucid. It seems like a larger rearchtiecting issue.