rik3k

Same 20MB/s during parity check. Writing to drives off parity-protected array gives me 150/160MB/s pretty consistently. I have a 2308 chipset HBA so I should be able to get much higher. It's really somehow tied to parity writes. CPU is barely touching 3% during transfers and plenty ram available. I did see a lot of documentation on the tunables but these seemed to apply to previous versions of Unraid. Newer version have less parameters and they don't seem to make much of an impact.

Turbo write enbaled/disabled also makes no difference. Unless a reboot is required to enable? Are you suggesting that perhaps I split the 'load' across multiple HBAs?

I have a dual parity array with 27 data disks (29 drives total). I simply cannot get the write speed to the array to go above 20mb/s. When I write to a cache drive (without parity) I have no issues. Tried disabling dockers/VMs, even tried single parity and the result is the same. Swapped out HBA cards, tried SATA parity vs SAS. Result is always the same. Tried playing around with Tunables but there does not seem to be an impact. Write caching enabled on all drives as well. Any thoughts? sodium-diagnostics-20210825-0828.zip

I have been running into this same issue but ultimately I am still bottlenecked by the transfer process. I plot in approx 45 minutes but the transfer process takes a bit longer (around 20MB/s). When I complete a 2nd plot, I now have Unraid transferring two plots on the same 20MB/s which slows everything down again. The ideal solution would be for Unraid to select a 2nd drive for the 2nd plot. Currently it always seems to pick the same drive for both file transfers. Any guidance on how to get Unraid to automatically pick another drive?

Suddenly I’m encountering a lot of ‘Seeking plots took too long’ issues and I really can’t pinpoint where they are coming from. CPU/RAM is not an issue as neither are anywhere close to maxed out. I shut off everything else (VM/dockers) and still have the same issue. Restarted the container. Drive read speeds don’t appear problematic. Logs don’t give much info except simply ‘plots took too long’. Any suggestions on where to look next? EDIT: OK I have found my issue. I plot with madmax in ram/nvme but phase 5:0 was holding me up. I am using an SSD cache on my Chiaplot share to speed up the process. However, I can only copy from my cache to the main array at approx 20mb/s, which is slower than I plot. Over time my cache fills up. If I disable cache completely, I get 50mb/s from my nvme direct to array. I solved this by allowing a 2nd plot to start at phase 5 but I wonder what is causing this behavior. I thought it was due to the container polling the plots on the cache drive but this speed persists even with the docker container shut down.

Hey, thanks for replying and also thanks for developing this. For the record, the 'culprit' is the 2nd entry of plots_dir which doesn't have an edit button. That being said, I did change this one to the correct value (along with the first one). I also had to go into config.yaml and and manually add the 2nd folder. Now I have this in there: plot_directories: - /plotting2 - /plots - /plots,/plotting2 Everything works as intended now and I do see everything properly listed on the farming page. Thanks!

thanks. I did look around and took note of the issue with duplicate variables. I have ‘plots_dir’ twice but when I run it, the command outputs to -e ‘/plots’=‘/plots:/plots2’. Somehow it’s dropping the _dir. I still seem to have the issue but it’s not a big deal, I think it’s farming properly still.

Can anyone else list plots in other folders on the farming page? I have the /plots as the main file but recently created a non-parity pool for more space and I don’t see them listed there. My total appears to be OK, and the plotter can write to the new location, but all I see are the /plots and nothing else.

So on the Pools page I have an Payout instructions (pool will pay to this address): which is not my first wallet address. I assume this is the Wallet 2’s address but I cannot find this one anywhere. This key is just one I cannot find anywhere on my install.