Optimal settings for use on a low resource vps and how to purge the vfs cache. Since I am limited on storage I would like to limit the size of the "vfs" folder so that does not consume all of my storage when transferring large files such as 45GB files.
With the current settings I have I noticed the vfs folder continues to grow in size regardless of what --vfs-cache limits I impose.
The way I am using the mount is by directly downloading large files into it, through the use of Premiumize and aria2 to download files from Premiumize into the mount.
What is your rclone version (output from rclone version)
rclone v1.51.0
Which OS you are using and how many bits (eg Windows 7, 64 bit)
There are edge cases but most times no cache is better. Reddit and other places reference to use cache but that info is old.
If you want to reduce memory usage on the micro, i typically lower or set the --buffer-size to zero. I also use --use-mmap for better memory management.
Also you may just want to set a small swap file to give some cushion.
Yes. Its free. There are other 'charges' if you can avoid them like egress/ingress. If you're just using this thing to transfer from/to google drives and other google services, you'll be in the free tier.
So I am transferring a 54GB file now using command rclone mount gcrypt: /mnt/GDrive -vv --daemon --allow-other --vfs-cache-mode writes --buffer-size 0 --use-mmap
However it looks like its continuously using up my disk space. I have paused the transfer as I only have 4.3GB remaining on the VPS. Should I disable --vfs-cache-mode writes?
Log:
2020/05/27 17:04:20 DEBUG : rclone: Version "v1.51.0" starting with parameters ["rclone" "mount" "gcrypt:" "/mnt/GDrive" "-vv" "--daemon" "--allow-other" "--vfs-cache-mode" "writes" "--buffer-size" "0" "--use-mmap"]
2020/05/27 17:04:20 DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
2020/05/27 17:04:21 DEBUG : rclone: Version "v1.51.0" finishing with parameters ["rclone" "mount" "gcrypt:" "/mnt/GDrive" "-vv" "--daemon" "--allow-other" "--vfs-cache-mode" "writes" "--buffer-size" "0" "--use-mmap"]
Only reason I am using a mount is because I am using Premiumizer's web interface to manage my Premiumize cloud downloads.
Once a file is downloaded to my cloud I can use the interface to download it to a local folder. In this case my "local" folder is the GDrive mount.
I have used copy/move before without any problems, the only downside was that I needed to always open up a ssh shell and run the command manually. The benefit of the Premiumizer web interface is that I can do everything with just a single click. Also, I can share the web link with others and let them download into my GDrive as well.
Looks like it works.. but it takes a few minutes for the transfer speed to ramp up, and even then its at most half of what the speed used to be. I will need to test out using vfs-cache minimal to see if there are any improvements.
On a side note, so if using cache is not useful anymore, should I be disabling even when I use a mount with Plex, or is that a situation where it can be used? I have a VPS with a pretty fast connection running my GDrive mount with Plex. It is currently using vfs-cache writes and I am using a cache remote wrapped around a gdrive remote.
I dont think there will be. The difference really is that when you're copying to the mount, its immediately transferring and so you'll need to wait for that to complete. It also won't have retries in the same way so if the transfer fails you'll need to reupload.
you don't need it for plex. That is a few year old problem. You may not even need vfs-cache-mode writes but that just depends on if/how your'e writing to it.