AaronY

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!

Tbh at this day and age, no API support on a network-operation-centric system is unheard of. I switched from TrueNas not even thinking about the availability of APIs being a potential issue (this is on me). Then, finding the unofficial Unraid-API only to realize that it hasn't been updated for 2 years with the repo owner understandably not interested in maintaining it, presumably because of the sheer amount of work needed to build a web scraper and maintain it for exponentially increasing versions of the webpages (multiple versions of unRaid, infinite combinations of plugins). This feature has been a long time waiting to be solved. @willnnotdan mentioned in the discord that an API was promised to be released with version 6.8 and that was almost three years ago. Oh and this feature request was posted more than 6 years ago... Please Lime Tech, show us some love, give us an api.