I am working with a mounted remote of type crypt that is located on a subfolder on a Google Drive (see command line below).
So far the vfs cache seems to work great for file read and write operations, but whenever I delete files interactively in Windows Explorer, that operation does not appear to be cached.
As an example I recently deleted a directory tree containing a few thousand files and directories on my google-workspace-vault: remote in Windows Explorer and that delete operation proceeded at the rate of about 1-2 files per second (according to the Windows Progress Indicator).
Am I missing a parameter that would also cache/buffer interactive file delete operations or is this simply not implemented? I realize that there might be more performant ways to accomplish this task of mass file deletion (perhaps via direct rclone commands?), but I'm enjoying the seamless integration into Explorer and would prefer to work through the Windows UI.
Just to be clear I don't care how long a cached delete operation might take in the background, it would just be nice to have the "interactive" part of the deletion finish quicker than it does in my current configuration. So can I do something to improve that?
FWIW my WinFSP version is 1.9.21096
I'm accessing a mounted remote of type crypt that points to a subfolder on Google Drive (which comes with a Google Workspace account).
My mount command line is
rclone mount google-workspace-vault: V: --volname "Google Workspace RCrypt Vault" --drive-acknowledge-abuse --network-mode --vfs-cache-mode full --vfs-cache-max-size 64G --daemon-timeout 599s --bwlimit 1200k -v
The issue/observation itself happens during direct interaction (file deletion in Windows Explorer).
[google-workspace] type = drive client_id = *** client_secret = *** scope = drive token = *** team_drive = [google-workspace-vault] type = crypt remote = google-workspace:rcrypt_vault password = ***
Due to the length of the logfile I'm just providing a link here: Dropbox - rclone_log_delete_files.txt - Simplify your life
Please note that the file delete operation that I logged was done with only a small quantity of files to avoid making the log even more bloated.