- #FREEFILESYNC GOOGLE DRIVE HOW TO#
- #FREEFILESYNC GOOGLE DRIVE FULL#
- #FREEFILESYNC GOOGLE DRIVE SOFTWARE#
#FREEFILESYNC GOOGLE DRIVE SOFTWARE#
I'm using the donation edition in part because I wanted to donate to a product that I use, and I use a fair amount of open source software and I typically donate to the ones that I use regularly. What I do not know is if the free version is limited to fewer file operations simultaneously than the donation edition is by default so the maximum number of threads might be different in the free versus the paid I do not know the answer to that you'll have to wait for a response from the developer.
It doesn't matter what you set the numbers to it never gets any better than what you get with them set at one each. I got less than three megabytes per second often less than developer seems to be correct. I ran some tests with regular document size files office document type files and my performance basically sucked. Could you test the parallel operations with like 5-10MB worth of 0-10KB files instead to measure if parallel operations increase the number of API requests that can be made?Īlso was your local drive an SSD or an HDD? I see you tested with fairly large files (only about 100 files with 7GB total), which basically removes the API request limits set by google to test bandwidth of the rest of the pipeline, since few of those files would be downloaded in less than 1 second.
I went from less than 10 MB/sec to almost 40 MB /sec. Increasing the parallel file operations for the local side made a BIG difference! MUCH better performance. I chose 10.Ĭhanging the Google side had NO effect on performance.
With the donation edition (I have) parallel file operations can be increased from one to a higher number for either the local file system or the Google file system or both. Also tried the Gnome one in Mint but FFS couldn't read the files at all without garbling them up.ĭon't bother wasting time with google-drive-ocamlfuse.
#FREEFILESYNC GOOGLE DRIVE FULL#
After the initial sync, when I only have to "update" the files, it's not so bad (I made the thread just after I did my first full sync which took like half a day).īut if you have the donate version of FFS and would be willing to test whether using the parallel file operations improves performance, that would be appreciated.ĭid some performance testing to compare google-drive-ocamlfuse to native freefilesync for google drive. Also command line stuff is a last resort kind of thing for me, I'd rather keep using (just) FFS despite the bad speed. That's also why I didn't want to use the integrated gnome utility that can do the same. I came across that one too, but I dismissed it because I don't want to mount the drive, since that doesn't create a local copy, so I wouldn't be able to access the files while offline. perhaps they operate at similar speed or perhaps one is faster than the other I don't know. I will run a brief performance test comparing free file sync on Linux and windows using this Google Drive Software to the free file sync Google drive functionality that's built into the app.
#FREEFILESYNC GOOGLE DRIVE HOW TO#
It's been a while since you have been up here reading this thread So I will hold off on posting detailed instructions on how to use the command until I know that you're going to get the instructions and you're still interested. Donation receives lifetime updates and unlimited installsįYI, there is a native Linux command line app that you use to mount Google Drive directly on Linux.
0 kommentar(er)
