Syncing with Google Drive is super slow

[dzek69]

I'm doing initial sync, I have 300 Mbps fibre connection. I'm on Linux right now.

Native Windows client can sync the changes on my account in few minutes, overGrive on Linux can do that too (if it not bugs).

Idk if this is a Celeste issue or rclone, but with Celeste I'm getting very slow updates for Checking 'path/to/the/file' on remote for changes. It's taking 3-5 seconds for each file. And I happen to have a bunch of small files in one folder.

Also this message suggests like a check to prevent issues when a file is updated both locally and on cloud at the same time - this is not needed at all on initial sync if I'm syncing to an empty folder. Maybe there is a way to disable that in such case to speed things up?

[ghost]

It's quite slow for me to when it works that is currently getting this error #62

[hwittenborn]

I'll need to set some time to do some benchmarking, but I'm not quite sure why Google Drive syncing would be slower than other remote types. Celeste doesn't do anything special for Google Drive syncing, so my guess is rclone but again, I'll have to do some benchmarking.

Also this message suggests like a check to prevent issues when a file is updated both locally and on cloud at the same time

That's just used when it's checking if the local or remote file/folder changed since the last sync - Celeste needs to do that so it can determine if it needs to push or pull the changes for any given file/folder.

That might actually be part of the slowdown if it takes a while to obtain that information from Google Drive, I'll make sure to include that as part of my testing.

[eriolloan]

This is probably not related to the way Celeste handles Google Drive sync. I'm connecting to a Nextcloud server and I'm also experiencing the 'Checking for changes' messages being displayed for quite a few second. The initial sync on a 13mb folder (only small files) has been checking for local changes for half an hour now.

I ruled out my bandwidth as a cause and it's not related to the server either as the Nextcloud Qt client was ok syncing huge folders earlier today.

[hwittenborn]

Thanks for the note @eriolloan, I'm not quite sure why it'd be happening even on a 13mb folder though. I'm finishing up AppImage packaging up for Celeste at the moment (I've had to write a new tool from scratch because none of the existing tooling to do it worked well, but that's almost done), and then I'm getting this and some other high-priority issues tacked.