November 29, 20223 yr Hi there, I am running my server on an really old i5-6600 with one parity drive and a couple of data drives. I have a docker container setup to automatically back up the content of my array (via /mnt/user ) to a cloud provider. Now I am not sure how their software scans files/disks, but every time this container runs, shfs pins a core to 100%(which is fine), but it is also causing a lot of iowait shown in above picture. I am wondering if there is a way to mitigate this issue. After some research I conducted a while ago (so its all kind of fuzzy for me right now), I believe I read somewhere that directly reading a drive (as in via /mnt/disk1, /mnt/disk2) could potentially lower the shfs overhead. Is this true? What other ways can I lower the iowait/shfs overhead? I have moved my appdata and docker.img to cache so those are not contributing factors to the iowait anymore. Thanks! Edited November 29, 20223 yr by AaronY typo
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.