Constantly high IOWAIT (add log)

[Rootax]

Will the future vfs read caching system help with some seeking/read paterns ?

[ncw (Nick Craig-Wood)]

@random404

Can you expand on that ? I often have the same file opened multiple times in the mount. I believe lots of people do the same

If two people are reading from the same file then rclone will continually seek back and forth. It will work, but it will be slow...

@Rootax

Will the future vfs read caching system help with some seeking/read paterns ?

The future --vfs-cache-mode full will fix this problem

[random404]

The future --vfs-cache-mode full will fix this problem

Why future? If I use that cache mode currently it won't work ?

I often have like 20 or more concurrently access to the same file. I never noticed any issues, but I had no idea rclone didn't handle that well...

Maybe this could be the reason of so much iowait and failed to wait errors too for other peoples as well.

If someone have usage patterns similars to mine, is it better to use async or sync reads?

[ncw (Nick Craig-Wood)]

@random404

Why future? If I use that cache mode currently it won't work ?

If you use it now it will download the entire file before serving it which probably isn't what you want.

[Dual-O (Oli)]

@Dual-O

Will test --async-read=true from now on to give more feedback

FYI: during (Emby) Libary Scan I got this constantly high IOWAIT back but this is not a issue. This is because the mount has to touch every file in mount sequential...

P.S. v1.52 works great with my Setup (Ubuntu 20.04 | Kernel 5.4.0 | rclone v1.52.0)

@ncw

The future --vfs-cache-mode full will fix this problem

looking forward to the new --vfs-cache-mode full ... this would be awesome

[ncw (Nick Craig-Wood)]

@Dual-O

P.S. v1.52 works great with my Setup (Ubuntu 20.04 | Kernel 5.4.0 | rclone v1.52.0

Great! Thanks for testing