jbartlett

I just kicked off a fullauto with version 2.2 with the following changes: Setting TestLen to 599 instead of 239 (in 3 places in the full-auto logic) to run for 10 minutes in order to get past my 32GB SSD drive which seems to skew the results. System specs MB: ASUSTeK Computer INC. - M4A88TD-V EVO/USB3 CPU: AMD Phenom II X4 965 - 3.4 GHz RAM: 4GB HD: 1.5TB WD EARS (3, jumpered), 2TB WD (1), 3TB Seagate (3), 4TB Seagate (2+parity), 32GB SSD (1), 500GB WD (Cache) Hard drives are connected to MB and to two PCI-E SATA extenders. Been replacing the EARS drives, one a month, with the 4TB Seagates. Preclearing another 4TB now. -John

Interesting. Seems the lowest possible setting is the best setting for me. Tunables Report from unRAID Tunables Tester v2.1 by Pauven NOTE: Use the smallest set of values that produce good results. Larger values increase server memory use, and may cause stability issues with unRAID, especially if you have any add-ons or plug-ins installed. Test | num_stripes | write_limit | sync_window | Speed --------------------------------------------------------------------------- 1 | 896 | 768 | 128 | 83.5 MB/s 2 | 1024 | 768 | 256 | 82.9 MB/s 3 | 1280 | 768 | 384 | 80.1 MB/s 4 | 1408 | 768 | 512 | 74.6 MB/s 5 | 1536 | 768 | 640 | 66.9 MB/s Completed: 0 Hrs 52 Min 20 Sec. Best Bang for the Buck: Test 1 with a speed of 83.5 MB/s Tunable (md_num_stripes): 896 Tunable (md_write_limit): 768 Tunable (md_sync_window): 128 These settings will consume 35MB of RAM on your hardware. Unthrottled values for your server came from Test 1 with a speed of 83.5 MB/s Tunable (md_num_stripes): 896 Tunable (md_write_limit): 768 Tunable (md_sync_window): 128 These settings will consume 35MB of RAM on your hardware. This is -15MB less than your current utilization of 50MB. NOTE: Adding additional drives will increase memory consumption. In unRAID, go to Settings > Disk Settings to set your chosen parameter values.

The drive itself isn't the unraid cache drive, it just holds cache data for my xbmc clients so there's no spin-up delay. Off to run 2.1, even before upgrading to 5.0 final!

That would be great if you could add support for lower ranges. I have a cheap 32GB SSD in my array that I use for caching purposes and while it's sustained read rating shouldn't have any affect, it clearly does. Running the 10 minute test which took my array to 1% on the parity check and well beyond the 32GB range, I saw much smoother results. I ran another test continuing the high range and it hovered around a .7 MB span. -John Tunables Report from unRAID Tunables Tester v2.0 by Pauven NOTE: Use the smallest set of values that produce good results. Larger values increase server memory use, and may cause stability issues with unRAID, especially if you have any add-ons or plug-ins installed. Test | num_stripes | write_limit | sync_window | Speed --------------------------------------------------------------------------- 1 | 1280 | 768 | 384 | 80.2 MB/s 2 | 1408 | 768 | 512 | 72.4 MB/s 3 | 1536 | 768 | 640 | 65.6 MB/s 4 | 1664 | 768 | 768 | 60.6 MB/s 5 | 1920 | 896 | 896 | 59.1 MB/s 6 | 2176 | 1024 | 1024 | 56.3 MB/s 7 | 2560 | 1152 | 1152 | 55.0 MB/s 8 | 2816 | 1280 | 1280 | 56.7 MB/s 9 | 3072 | 1408 | 1408 | 54.6 MB/s 10 | 3328 | 1536 | 1536 | 58.0 MB/s 11 | 3584 | 1664 | 1664 | 54.0 MB/s 12 | 3968 | 1792 | 1792 | 54.5 MB/s 13 | 4224 | 1920 | 1920 | 54.5 MB/s 14 | 4480 | 2048 | 2048 | 51.4 MB/s Completed: 2 Hrs 26 Min 23 Sec. Best Bang for the Buck: Test 1 with a speed of 80.2 MB/s Tunable (md_num_stripes): 1280 Tunable (md_write_limit): 768 Tunable (md_sync_window): 384 These settings will consume 50MB of RAM on your hardware. Unthrottled values for your server came from Test 1 with a speed of 80.2 MB/s Tunable (md_num_stripes): 1280 Tunable (md_write_limit): 768 Tunable (md_sync_window): 384 These settings will consume 50MB of RAM on your hardware. This is -20MB less than your current utilization of 70MB. NOTE: Adding additional drives will increase memory consumption. In unRAID, go to Settings > Disk Settings to set your chosen parameter values.

Question - at the end of the test, it states that you should stop & start the array. Would it be wise to request the user to do it prior to testing as well? I ran full-auto twice and received results that jumped all over the place. Only one test scored the same both times, the others had differences as much as 6 mb/sec. Is the later typical? Currently running the Extreme test (10 min) with default selections to see if it gives a bell curve that I expect the results should reflect. Tunables Report from unRAID Tunables Tester v2.0 by Pauven NOTE: Use the smallest set of values that produce good results. Larger values increase server memory use, and may cause stability issues with unRAID, especially if you have any add-ons or plug-ins installed. Test | num_stripes | write_limit | sync_window | Speed --- FULLY AUTOMATIC TEST PASS 1 (Rough - 20 Sample Points @ 3min Duration)--- 1 | 1408 | 768 | 512 | 71.1 MB/s 2 | 1536 | 768 | 640 | 63.8 MB/s 3 | 1664 | 768 | 768 | 60.0 MB/s 4 | 1920 | 896 | 896 | 61.7 MB/s 5 | 2176 | 1024 | 1024 | 56.7 MB/s 6 | 2560 | 1152 | 1152 | 58.4 MB/s 7 | 2816 | 1280 | 1280 | 58.5 MB/s 8 | 3072 | 1408 | 1408 | 56.6 MB/s 9 | 3328 | 1536 | 1536 | 54.0 MB/s 10 | 3584 | 1664 | 1664 | 55.5 MB/s 11 | 3968 | 1792 | 1792 | 56.8 MB/s 12 | 4224 | 1920 | 1920 | 51.4 MB/s 13 | 4480 | 2048 | 2048 | 56.4 MB/s 14 | 4736 | 2176 | 2176 | 54.4 MB/s 15 | 5120 | 2304 | 2304 | 54.1 MB/s 16 | 5376 | 2432 | 2432 | 53.7 MB/s 17 | 5632 | 2560 | 2560 | 49.8 MB/s 18 | 5888 | 2688 | 2688 | 54.7 MB/s 19 | 6144 | 2816 | 2816 | 52.9 MB/s 20 | 6528 | 2944 | 2944 | 51.1 MB/s --- Targeting Fastest Result of md_sync_window 512 bytes for Medium Pass --- --- FULLY AUTOMATIC TEST PASS 2 (Final - 16 Sample Points @ 4min Duration)--- 21 | 1288 | 768 | 392 | 80.0 MB/s 22 | 1296 | 768 | 400 | 77.5 MB/s 23 | 1304 | 768 | 408 | 75.8 MB/s 24 | 1312 | 768 | 416 | 77.9 MB/s 25 | 1320 | 768 | 424 | 76.2 MB/s 26 | 1328 | 768 | 432 | 74.7 MB/s 27 | 1336 | 768 | 440 | 74.4 MB/s 28 | 1344 | 768 | 448 | 74.4 MB/s 29 | 1360 | 768 | 456 | 74.3 MB/s 30 | 1368 | 768 | 464 | 78.3 MB/s 31 | 1376 | 768 | 472 | 77.4 MB/s 32 | 1384 | 768 | 480 | 74.6 MB/s 33 | 1392 | 768 | 488 | 72.7 MB/s 34 | 1400 | 768 | 496 | 74.4 MB/s 35 | 1408 | 768 | 504 | 74.5 MB/s 36 | 1416 | 768 | 512 | 73.8 MB/s Completed: 2 Hrs 9 Min 8 Sec. Best Bang for the Buck: Test 1 with a speed of 71.1 MB/s Tunable (md_num_stripes): 1408 Tunable (md_write_limit): 768 Tunable (md_sync_window): 512 These settings will consume 55MB of RAM on your hardware. Unthrottled values for your server came from Test 21 with a speed of 80.0 MB/s Tunable (md_num_stripes): 1288 Tunable (md_write_limit): 768 Tunable (md_sync_window): 392 These settings will consume 50MB of RAM on your hardware. This is -20MB less than your current utilization of 70MB. NOTE: Adding additional drives will increase memory consumption. In unRAID, go to Settings > Disk Settings to set your chosen parameter values.

I did. kill -9 did not kill it.

I had an odd thing happen yesterday. The permission on one of my drives were messed up which prevented the files on that particular drive from showing up in the shares. I kicked off the permission fix tool from the UNRAID GUI. It hit the drive with the bad permissions and seemed to be taking an extraordinary amount of time on it. The UNRAID GUI was unresponsive trying to pull it up in a new window. UnMenu displayed but showed that there was no disk activity on disk20 which was currently being "fixed". I telnetted in and stopped the cache-dir script and it reported it successfully stopped. However, top still reported it was running. I was unable to kill the PID for it nor the PID for the task that was running the "find" command or the chmod command that UNRAID was running. I commented out the script in the go file and ungracefully powered down UNRAID. Upon reboot, the permission script ran without issue. Re-enabled the cache-dir script. Reran the permission fix script and it ran without issue.