drive
drive copied to clipboard
Slow Pull
Hi, i have changed one file on a folder with multiples subfolders. Total folder is 600mb.
I created a cron to run the pull every 30 seconds, since I used the dropbox and it identified the changes. The point is the pull is taking a lot. You get the message "Resolving ..." and nothing to finish the pull, and only one file was changed. How could you not be so slow?
If i use drive pull -fix-clashes -no-prompt -ignore-name-clashes -ignore-checksum=false -depth 2 4UWeb/clientes
The pull is very fast because only sync that folder, but i need sync all sub folders and this is very slow...
The client fetches a chunk of 1000 files metadata at a time, which can be slow if you have many thousands of files. It is even slower when you have lots of subfolders, as each of them counts as a file and new request must be made in order to get its children. Not much you can do to improve speed here!
@stewartmcgown Is that a limitation of drive
or the API used?
Google Drive's API
Would it be possible to get an option to show these calls? I am playing with drive
right now, and with a fairly large share it has been "resolving" for a bit over 5 minutes so far.
Watching my network activity I'm only seeing about 15 kB/s, so I assume this is just the server API being very slow, but it would be nice to confirm that drive
has not hung or stuck.