Was there a default md_write_limit ? I'm trying different numbers and backup file says the default was 1152, but that doesn't look right. I may boot up my other pro key and see what the defaults were.

 

Anyway, I ran the script and it indicated 108MB/sec read speeds. With the defaults I got 111MB/sec. So I changed the tunable numbers anyway to give it a shot, rebooted and my read speeds were horrible! They were at 25MB/sec! Went back to defaults, reboot and they went back to 111MB/sec. I think I'm done with playing around with this script. I'll stick with 111MB/sec read speeds.

 

Updated since I doubled RAM and removed slower EARS drives from array. Interesting to note it took me back to values I got from the first time I ran it but added 38 MB/s to speed.

 

 

Tunables Report from  unRAID Tunables Tester v2.2 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     |  97.2 MB/s 
   2  |    1536     |     768     |     640     | 104.4 MB/s 
   3  |    1664     |     768     |     768     | 104.0 MB/s 
   4  |    1920     |     896     |     896     | 104.7 MB/s 
   5  |    2176     |    1024     |    1024     | 103.9 MB/s 
   6  |    2560     |    1152     |    1152     |  97.5 MB/s 
   7  |    2816     |    1280     |    1280     | 100.4 MB/s 
   8  |    3072     |    1408     |    1408     | 102.6 MB/s 
   9  |    3328     |    1536     |    1536     |  99.6 MB/s 
  10  |    3584     |    1664     |    1664     | 103.1 MB/s 
  11  |    3968     |    1792     |    1792     | 102.5 MB/s 
  12  |    4224     |    1920     |    1920     | 102.9 MB/s 
  13  |    4480     |    2048     |    2048     | 100.7 MB/s 
  14  |    4736     |    2176     |    2176     | 102.1 MB/s 
  15  |    5120     |    2304     |    2304     | 102.0 MB/s 
  16  |    5376     |    2432     |    2432     | 102.2 MB/s 
  17  |    5632     |    2560     |    2560     | 101.5 MB/s 
  18  |    5888     |    2688     |    2688     | 102.1 MB/s 
  19  |    6144     |    2816     |    2816     | 102.2 MB/s 
  20  |    6528     |    2944     |    2944     | 101.4 MB/s 
--- Targeting Fastest Result of md_sync_window 896 bytes for Final Pass ---
--- FULLY AUTOMATIC TEST PASS 2 (Final - 16 Sample Points @ 4min Duration)---
  21  |    1720     |     776     |     776     |  91.6 MB/s 
  22  |    1736     |     784     |     784     |  90.6 MB/s 
  23  |    1760     |     792     |     792     |  90.6 MB/s 
  24  |    1776     |     800     |     800     |  90.3 MB/s 
  25  |    1792     |     808     |     808     |  92.7 MB/s 
  26  |    1808     |     816     |     816     |  91.1 MB/s 
  27  |    1824     |     824     |     824     |  93.2 MB/s 
  28  |    1848     |     832     |     832     |  91.9 MB/s 
  29  |    1864     |     840     |     840     |  92.2 MB/s 
  30  |    1880     |     848     |     848     |  91.7 MB/s 
  31  |    1896     |     856     |     856     |  91.8 MB/s 
  32  |    1920     |     864     |     864     |  92.6 MB/s 
  33  |    1936     |     872     |     872     |  92.6 MB/s 
  34  |    1952     |     880     |     880     |  91.3 MB/s 
  35  |    1968     |     888     |     888     |  92.3 MB/s 
  36  |    1984     |     896     |     896     |  94.6 MB/s 

Completed: 2 Hrs 11 Min 13 Sec.

Best Bang for the Buck: Test 2 with a speed of 104.4 MB/s

     Tunable (md_num_stripes): 1536
     Tunable (md_write_limit): 768
     Tunable (md_sync_window): 640

These settings will consume 66MB of RAM on your hardware.


Unthrottled values for your server came from Test 36 with a speed of 94.6 MB/s

     Tunable (md_num_stripes): 1984
     Tunable (md_write_limit): 896
     Tunable (md_sync_window): 896

These settings will consume 85MB of RAM on your hardware.
This is 25MB more than your current utilization of 60MB.
NOTE: Adding additional drives will increase memory consumption.

In unRAID, go to Settings > Disk Settings to set your chosen parameter values.

 

 

New (to me) ARC-1231ML RAID controller (JBOD mode) with nice performance bump over the AOC-SASLP-MV8 it replaced.

 

Tunables Report from  unRAID Tunables Tester v2.2 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     |  98.8 MB/s 
   2  |    1536     |     768     |     640     |  93.9 MB/s 
   3  |    1664     |     768     |     768     |  75.1 MB/s 
   4  |    1920     |     896     |     896     |  72.6 MB/s 
   5  |    2176     |    1024     |    1024     |  73.0 MB/s 
   6  |    2560     |    1152     |    1152     |  72.9 MB/s 
   7  |    2816     |    1280     |    1280     |  72.9 MB/s 
   8  |    3072     |    1408     |    1408     |  74.2 MB/s 
   9  |    3328     |    1536     |    1536     |  73.3 MB/s 
  10  |    3584     |    1664     |    1664     |  72.6 MB/s 
  11  |    3968     |    1792     |    1792     |  73.6 MB/s 
  12  |    4224     |    1920     |    1920     |  72.6 MB/s 
  13  |    4480     |    2048     |    2048     |  72.8 MB/s 
  14  |    4736     |    2176     |    2176     |  71.6 MB/s 
  15  |    5120     |    2304     |    2304     |  73.0 MB/s 
  16  |    5376     |    2432     |    2432     |  71.7 MB/s 
  17  |    5632     |    2560     |    2560     |  73.0 MB/s 
  18  |    5888     |    2688     |    2688     |  74.3 MB/s 
  19  |    6144     |    2816     |    2816     |  73.1 MB/s 
  20  |    6528     |    2944     |    2944     |  71.6 MB/s 
--- Targeting Fastest Result of md_sync_window 512 bytes for Special Pass ---
--- FULLY AUTOMATIC TEST PASS 1b (Rough - 4 Sample Points @ 3min Duration)---
  21  |    896     |     768     |     128     |  57.0 MB/s 
  22  |    1024     |     768     |     256     |  74.0 MB/s 
  23  |    1280     |     768     |     384     |  85.5 MB/s 
  24  |    1408     |     768     |     512     |  90.5 MB/s 
--- Targeting Fastest Result of md_sync_window 512 bytes for Final Pass ---
--- FULLY AUTOMATIC TEST PASS 2 (Final - 16 Sample Points @ 4min Duration)---
  25  |    1288     |     768     |     392     |  86.1 MB/s 
  26  |    1296     |     768     |     400     |  85.6 MB/s 
  27  |    1304     |     768     |     408     |  86.6 MB/s 
  28  |    1312     |     768     |     416     |  87.1 MB/s 
  29  |    1320     |     768     |     424     |  87.5 MB/s 
  30  |    1328     |     768     |     432     |  88.3 MB/s 
  31  |    1336     |     768     |     440     |  88.3 MB/s 
  32  |    1344     |     768     |     448     |  88.6 MB/s 
  33  |    1360     |     768     |     456     |  88.8 MB/s 
  34  |    1368     |     768     |     464     |  89.2 MB/s 
  35  |    1376     |     768     |     472     |  89.4 MB/s 
  36  |    1384     |     768     |     480     |  89.4 MB/s 
  37  |    1392     |     768     |     488     |  90.2 MB/s 
  38  |    1400     |     768     |     496     |  89.9 MB/s 
  39  |    1408     |     768     |     504     |  90.7 MB/s 
  40  |    1416     |     768     |     512     |  90.9 MB/s 

Completed: 2 Hrs 24 Min 48 Sec.

Best Bang for the Buck: Test 1 with a speed of 98.8 MB/s

     Tunable (md_num_stripes): 1408
     Tunable (md_write_limit): 768
     Tunable (md_sync_window): 512

These settings will consume 71MB of RAM on your hardware.


Unthrottled values for your server came from Test 40 with a speed of 90.9 MB/s

     Tunable (md_num_stripes): 1416
     Tunable (md_write_limit): 768
     Tunable (md_sync_window): 512

These settings will consume 71MB of RAM on your hardware.
This is -7MB less than your current utilization of 78MB.
NOTE: Adding additional drives will increase memory consumption.

In unRAID, go to Settings > Disk Settings to set your chosen parameter values.

 

I applied the Best Bang for the Buck settings. I am appalled at my disk speeds tho.

 

Tunables Report from  unRAID Tunables Tester v2.2 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     |  65.8 MB/s 
   2  |    1536     |     768     |     640     |  66.6 MB/s 
   3  |    1664     |     768     |     768     |  66.8 MB/s 
   4  |    1920     |     896     |     896     |  66.9 MB/s 
   5  |    2176     |    1024     |    1024     |  67.2 MB/s 
   6  |    2560     |    1152     |    1152     |  67.8 MB/s 
   7  |    2816     |    1280     |    1280     |  68.8 MB/s 
   8  |    3072     |    1408     |    1408     |  69.0 MB/s 
   9  |    3328     |    1536     |    1536     |  68.5 MB/s 
  10  |    3584     |    1664     |    1664     |  69.1 MB/s 
  11  |    3968     |    1792     |    1792     |  68.9 MB/s 
  12  |    4224     |    1920     |    1920     |  69.1 MB/s 
  13  |    4480     |    2048     |    2048     |  69.0 MB/s 
  14  |    4736     |    2176     |    2176     |  69.1 MB/s 
  15  |    5120     |    2304     |    2304     |  69.0 MB/s 
  16  |    5376     |    2432     |    2432     |  68.6 MB/s 
  17  |    5632     |    2560     |    2560     |  68.9 MB/s 
  18  |    5888     |    2688     |    2688     |  69.3 MB/s 
  19  |    6144     |    2816     |    2816     |  69.4 MB/s 
  20  |    6528     |    2944     |    2944     |  69.0 MB/s 
--- Targeting Fastest Result of md_sync_window 2816 bytes for Final Pass ---
--- FULLY AUTOMATIC TEST PASS 2 (Final - 16 Sample Points @ 4min Duration)---
  21  |    5984     |    2696     |    2696     |  69.0 MB/s 
  22  |    6008     |    2704     |    2704     |  69.0 MB/s 
  23  |    6024     |    2712     |    2712     |  69.3 MB/s 
  24  |    6040     |    2720     |    2720     |  69.0 MB/s 
  25  |    6056     |    2728     |    2728     |  69.0 MB/s 
  26  |    6080     |    2736     |    2736     |  68.9 MB/s 
  27  |    6096     |    2744     |    2744     |  69.1 MB/s 
  28  |    6112     |    2752     |    2752     |  69.0 MB/s 
  29  |    6128     |    2760     |    2760     |  69.2 MB/s 
  30  |    6144     |    2768     |    2768     |  68.6 MB/s 
  31  |    6168     |    2776     |    2776     |  69.1 MB/s 
  32  |    6184     |    2784     |    2784     |  69.1 MB/s 
  33  |    6200     |    2792     |    2792     |  68.8 MB/s 
  34  |    6216     |    2800     |    2800     |  68.8 MB/s 
  35  |    6240     |    2808     |    2808     |  69.3 MB/s 
  36  |    6256     |    2816     |    2816     |  68.9 MB/s 

Completed: 2 Hrs 14 Min 4 Sec.

Best Bang for the Buck: Test 2 with a speed of 66.6 MB/s

     Tunable (md_num_stripes): 1536
     Tunable (md_write_limit): 768
     Tunable (md_sync_window): 640

These settings will consume 78MB of RAM on your hardware.


Unthrottled values for your server came from Test 23 with a speed of 69.3 MB/s

     Tunable (md_num_stripes): 6024
     Tunable (md_write_limit): 2712
     Tunable (md_sync_window): 2712

These settings will consume 305MB of RAM on your hardware.
This is 240MB more than your current utilization of 65MB.
NOTE: Adding additional drives will increase memory consumption.

In unRAID, go to Settings > Disk Settings to set your chosen parameter values.

This appears to be broken due to the recent changes in /root/mdcmd in the 6.1 RCs...

 

unRAID Tunables Tester v2.2 by Pauven
./unraid-tunables-tester.sh: line 80: /root/mdcmd: No such file or directory

./unraid-tunables-tester.sh: line 388: /root/mdcmd: No such file or directory
./unraid-tunables-tester.sh: line 389: /root/mdcmd: No such file or directory
./unraid-tunables-tester.sh: line 390: /root/mdcmd: No such file or directory
./unraid-tunables-tester.sh: line 394: /root/mdcmd: No such file or directory
./unraid-tunables-tester.sh: line 397: /root/mdcmd: No such file or directory
./unraid-tunables-tester.sh: line 400: [: : integer expression expected
Test 1 - md_sync_window=384 - Test Range Entered - Time Remaining: 587s ^C

 

Anyone have a fix?

 

John

This appears to be broken due to the recent changes in /root/mdcmd in the 6.1 RCs...

 

unRAID Tunables Tester v2.2 by Pauven
./unraid-tunables-tester.sh: line 80: /root/mdcmd: No such file or directory

./unraid-tunables-tester.sh: line 388: /root/mdcmd: No such file or directory
./unraid-tunables-tester.sh: line 389: /root/mdcmd: No such file or directory
./unraid-tunables-tester.sh: line 390: /root/mdcmd: No such file or directory
./unraid-tunables-tester.sh: line 394: /root/mdcmd: No such file or directory
./unraid-tunables-tester.sh: line 397: /root/mdcmd: No such file or directory
./unraid-tunables-tester.sh: line 400: [: : integer expression expected
Test 1 - md_sync_window=384 - Test Range Entered - Time Remaining: 587s ^C

 

Anyone have a fix?

 

John

Edit the script with Notepad++

 

Replace all occurrances of /root/mdcmd with /usr/local/sbin/mdcmd

 

This appears to be broken due to the recent changes in /root/mdcmd in the 6.1 RCs...

 

unRAID Tunables Tester v2.2 by Pauven
./unraid-tunables-tester.sh: line 80: /root/mdcmd: No such file or directory

./unraid-tunables-tester.sh: line 388: /root/mdcmd: No such file or directory
./unraid-tunables-tester.sh: line 389: /root/mdcmd: No such file or directory
./unraid-tunables-tester.sh: line 390: /root/mdcmd: No such file or directory
./unraid-tunables-tester.sh: line 394: /root/mdcmd: No such file or directory
./unraid-tunables-tester.sh: line 397: /root/mdcmd: No such file or directory
./unraid-tunables-tester.sh: line 400: [: : integer expression expected
Test 1 - md_sync_window=384 - Test Range Entered - Time Remaining: 587s ^C

 

Anyone have a fix?

 

John

Edit the script with Notepad++

 

Replace all occurrances of /root/mdcmd with /usr/local/sbin/mdcmd

 

Or link where the command is to where the scripts want it to be...

 

ln -s /usr/local/sbin/mdcmd /root/mdcmd

 

Well this just confirms I really need a new server. See my results below.  Really jealous about the results I'm seeing in this topic. 

Though I must admit my drives are 5400rpm green drives. But didn't think they'd perform this sh*tty. Though standalone testing gives them almost 90 Mb/s each.

 

 

Tunables Report from  unRAID Tunables Tester v2.2 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     |  23.2 MB/s 
   2  |    1536     |     768     |     640     |  27.3 MB/s 
   3  |    1664     |     768     |     768     |  28.1 MB/s 
   4  |    1920     |     896     |     896     |  27.4 MB/s 
   5  |    2176     |    1024     |    1024     |  27.7 MB/s 
   6  |    2560     |    1152     |    1152     |  27.5 MB/s 
   7  |    2816     |    1280     |    1280     |  27.4 MB/s 
   8  |    3072     |    1408     |    1408     |  26.1 MB/s 
   9  |    3328     |    1536     |    1536     |  29.3 MB/s 
  10  |    3584     |    1664     |    1664     |  28.7 MB/s 
  11  |    3968     |    1792     |    1792     |  28.5 MB/s 
  12  |    4224     |    1920     |    1920     |  28.9 MB/s 
  13  |    4480     |    2048     |    2048     |  28.8 MB/s 
  14  |    4736     |    2176     |    2176     |  28.9 MB/s 
  15  |    5120     |    2304     |    2304     |  28.8 MB/s 
  16  |    5376     |    2432     |    2432     |  28.6 MB/s 
  17  |    5632     |    2560     |    2560     |  29.0 MB/s 
  18  |    5888     |    2688     |    2688     |  28.4 MB/s 
  19  |    6144     |    2816     |    2816     |  29.0 MB/s 
  20  |    6528     |    2944     |    2944     |  29.0 MB/s 
--- Targeting Fastest Result of md_sync_window 1536 bytes for Final Pass ---
--- FULLY AUTOMATIC TEST PASS 2 (Final - 16 Sample Points @ 4min Duration)---
  21  |    3144     |    1416     |    1416     |  28.0 MB/s 
  22  |    3160     |    1424     |    1424     |  28.8 MB/s 
  23  |    3176     |    1432     |    1432     |  28.5 MB/s 
  24  |    3200     |    1440     |    1440     |  29.0 MB/s 
  25  |    3216     |    1448     |    1448     |  29.1 MB/s 
  26  |    3232     |    1456     |    1456     |  29.1 MB/s 
  27  |    3248     |    1464     |    1464     |  29.0 MB/s 
  28  |    3264     |    1472     |    1472     |  28.3 MB/s 
  29  |    3288     |    1480     |    1480     |  29.0 MB/s 
  30  |    3304     |    1488     |    1488     |  29.6 MB/s 
  31  |    3320     |    1496     |    1496     |  28.8 MB/s 
  32  |    3336     |    1504     |    1504     |  28.8 MB/s 
  33  |    3360     |    1512     |    1512     |  28.5 MB/s 
  34  |    3376     |    1520     |    1520     |  26.3 MB/s 
  35  |    3392     |    1528     |    1528     |  29.0 MB/s 
  36  |    3408     |    1536     |    1536     |  28.9 MB/s 

 

 

And individual testing with the speedtest.sh script:

 

 

diskspeed.sh for UNRAID, version 2.4
By John Bartlett. Support board @ limetech: http://goo.gl/ysJeYV


/dev/sdb (Parity): 87 MB/sec avg
/dev/sdc (Disk 2): 88 MB/sec avg
/dev/sdd (Disk 1): 89 MB/sec avg

Just found this topic and was curious as to what is the difference between the speeds mentioned here and the speed from this command:

hdparm -tT /dev/sda

Just found this topic and was curious as to what is the difference between the speeds mentioned here and the speed from this command:

hdparm -tT /dev/sda

This utility tests the speed of parity checks using various tunable settings.  The hdparm will test a single drive.  Parity checks can be bottlenecked by the choice of controller cards, type of bus used, number of drives, etc.  A single drive will rarely (if ever) be affected by those constraints (unless you're testing an SSD)

What are the drives? I'd doubt the problem is with them since they're all scoring nearly the same assuming they did better previously.

In running this script in the fullauto mode my  lowest was 55.6 MB/s and the highest was 57.2 MB/s.

 

The Bang for the Buck is 56.7 MB/s and the un-throttled is 57.2 MB/s.

 

Does this mean on my system, these tunables do not make a big difference?  I will pay attention to what is the speed of my current settings at the next parity check.

I'd try a manual scan and specify rages on the far edges.

I ran the script on my mainserver and got results as shown in the attachment.

 

What would you advise me to use?

 

In 6.1.2 I can set these:

 

Tunable (poll_attributes)

 

Tunable (md_num_stripes)

 

Tunable (md_sync_window)

 

Where should I set the write limit value?

TunablesReport.zip

Poll_attributes is for reading disk temperatures, defaults to 1800sec, doesn’t affect speed unless set too low so it’s constantly polling the disks.

 

In Unraid 6 md_write_limit is not visible in the GUI, I don’t know if it’s still used but I still set it to the value recommend by tunnables, you can find all 3 settings in your flash /config/disk.cfg

 

As for what values to set I always choose unthrottled but it depends on the amount of RAM you have, settings will only take effect after rebooting.

 

Poll_attributes is for reading disk temperatures, defaults to 1800sec, doesn’t affect speed unless set too low so it’s constantly polling the disks.

 

In Unraid 6 md_write_limit is not visible in the GUI, I don’t know if it’s still used but I still set it to the value recommend by tunnables, you can find all 3 settings in your flash /config/disk.cfg

 

As for what values to set I always choose unthrottled but it depends on the amount of RAM you have, settings will only take effect after rebooting.

Thank you for the info. Can this be done without any risk? I have 16 GB of memory, so I might go with the untrottled settings.

Never had any problems and most of my servers only have 4Gb, but take note of original values just in case.

I had previously been getting around 95MB/sec parity check on my SAS2LP cards. I just swapped them out for M1015s and ended up with 82.6MB/sec, so decided to run the tunables script to optimize.

 

When I ran, I got the following:

 

Test | num_stripes | write_limit | sync_window |   Speed 
--- FULLY AUTOMATIC TEST PASS 1 (Rough - 20 Sample Points @ 3min Duration)---
   1  |    1408     |     768     |     512     | 118.0 MB/s 
   2  |    1536     |     768     |     640     | 118.2 MB/s 
   3  |    1664     |     768     |     768     | 118.2 MB/s 
   4  |    1920     |     896     |     896     | 118.2 MB/s 
   5  |    2176     |    1024     |    1024     | 118.2 MB/s 
   6  |    2560     |    1152     |    1152     | 118.2 MB/s 
   7  |    2816     |    1280     |    1280     | 118.2 MB/s 
   8  |    3072     |    1408     |    1408     | 118.2 MB/s 
   9  |    3328     |    1536     |    1536     | 118.2 MB/s 
  10  |    3584     |    1664     |    1664     | 118.2 MB/s 
  11  |    3968     |    1792     |    1792     | 118.2 MB/s 
  12  |    4224     |    1920     |    1920     | 118.2 MB/s 
  13  |    4480     |    2048     |    2048     | 118.2 MB/s 
  14  |    4736     |    2176     |    2176     | 118.2 MB/s 
  15  |    5120     |    2304     |    2304     | 118.2 MB/s 
  16  |    5376     |    2432     |    2432     | 118.2 MB/s 
  17  |    5632     |    2560     |    2560     | 118.2 MB/s 
  18  |    5888     |    2688     |    2688     | 118.2 MB/s 
  19  |    6144     |    2816     |    2816     | 118.2 MB/s 
  20  |    6528     |    2944     |    2944     | 118.2 MB/s 
--- Targeting Fastest Result of md_sync_window 640 bytes for Final Pass ---
--- FULLY AUTOMATIC TEST PASS 2 (Final - 16 Sample Points @ 4min Duration)---
  21  |    1424     |     768     |     520     | 118.2 MB/s 
  22  |    1440     |     768     |     528     | 118.2 MB/s 
  23  |    1448     |     768     |     536     | 118.2 MB/s 
  24  |    1456     |     768     |     544     | 118.2 MB/s 
  25  |    1464     |     768     |     552     | 118.2 MB/s 
  26  |    1472     |     768     |     560     | 118.2 MB/s 
  27  |    1480     |     768     |     568     | 118.2 MB/s 
  28  |    1488     |     768     |     576     | 118.2 MB/s 
  29  |    1496     |     768     |     584     | 118.2 MB/s 
  30  |    1504     |     768     |     592     | 118.2 MB/s 
  31  |    1520     |     768     |     600     | 118.3 MB/s 
  32  |    1528     |     768     |     608     | 118.2 MB/s 
  33  |    1536     |     768     |     616     | 118.3 MB/s 
  34  |    1544     |     768     |     624     | 118.2 MB/s 
  35  |    1552     |     768     |     632     | 118.3 MB/s 
  36  |    1560     |     768     |     640     | 118.3 MB/s 

Completed: 2 Hrs 9 Min 43 Sec.

Best Bang for the Buck: Test 1 with a speed of 118.0 MB/s

     Tunable (md_num_stripes): 1408
     Tunable (md_write_limit): 768
     Tunable (md_sync_window): 512

These settings will consume 126MB of RAM on your hardware.


Unthrottled values for your server came from Test 31 with a speed of 118.3 MB/s

     Tunable (md_num_stripes): 1520
     Tunable (md_write_limit): 768
     Tunable (md_sync_window): 600

These settings will consume 136MB of RAM on your hardware.
This is -422MB less than your current utilization of 558MB.
NOTE: Adding additional drives will increase memory consumption.

 

It looks really odd that all the values are virtually identical. Does this make sense? Is there a potential issue? I wasn't necessarily expecting dramatic variations, but did expect some differences.

 

Also, as a suggestion... it would be great if the tunables text file including the current settings for the 3 variables in it's output so they can be easily referenced again. I wasn't smart enough to write them down before making the change, but would like to have had this documented for reference in case of an issue.

 

 

I had previously been getting around 95MB/sec parity check on my SAS2LP cards. I just swapped them out for M1015s and ended up with 82.6MB/sec, so decided to run the tunables script to optimize.

 

When I ran, I got the following:

 

Test | num_stripes | write_limit | sync_window |   Speed 
--- FULLY AUTOMATIC TEST PASS 1 (Rough - 20 Sample Points @ 3min Duration)---
   1  |    1408     |     768     |     512     | 118.0 MB/s 
   2  |    1536     |     768     |     640     | 118.2 MB/s 
   3  |    1664     |     768     |     768     | 118.2 MB/s 
   4  |    1920     |     896     |     896     | 118.2 MB/s 
   5  |    2176     |    1024     |    1024     | 118.2 MB/s 
   6  |    2560     |    1152     |    1152     | 118.2 MB/s 
   7  |    2816     |    1280     |    1280     | 118.2 MB/s 
   8  |    3072     |    1408     |    1408     | 118.2 MB/s 
   9  |    3328     |    1536     |    1536     | 118.2 MB/s 
  10  |    3584     |    1664     |    1664     | 118.2 MB/s 
  11  |    3968     |    1792     |    1792     | 118.2 MB/s 
  12  |    4224     |    1920     |    1920     | 118.2 MB/s 
  13  |    4480     |    2048     |    2048     | 118.2 MB/s 
  14  |    4736     |    2176     |    2176     | 118.2 MB/s 
  15  |    5120     |    2304     |    2304     | 118.2 MB/s 
  16  |    5376     |    2432     |    2432     | 118.2 MB/s 
  17  |    5632     |    2560     |    2560     | 118.2 MB/s 
  18  |    5888     |    2688     |    2688     | 118.2 MB/s 
  19  |    6144     |    2816     |    2816     | 118.2 MB/s 
  20  |    6528     |    2944     |    2944     | 118.2 MB/s 
--- Targeting Fastest Result of md_sync_window 640 bytes for Final Pass ---
--- FULLY AUTOMATIC TEST PASS 2 (Final - 16 Sample Points @ 4min Duration)---
  21  |    1424     |     768     |     520     | 118.2 MB/s 
  22  |    1440     |     768     |     528     | 118.2 MB/s 
  23  |    1448     |     768     |     536     | 118.2 MB/s 
  24  |    1456     |     768     |     544     | 118.2 MB/s 
  25  |    1464     |     768     |     552     | 118.2 MB/s 
  26  |    1472     |     768     |     560     | 118.2 MB/s 
  27  |    1480     |     768     |     568     | 118.2 MB/s 
  28  |    1488     |     768     |     576     | 118.2 MB/s 
  29  |    1496     |     768     |     584     | 118.2 MB/s 
  30  |    1504     |     768     |     592     | 118.2 MB/s 
  31  |    1520     |     768     |     600     | 118.3 MB/s 
  32  |    1528     |     768     |     608     | 118.2 MB/s 
  33  |    1536     |     768     |     616     | 118.3 MB/s 
  34  |    1544     |     768     |     624     | 118.2 MB/s 
  35  |    1552     |     768     |     632     | 118.3 MB/s 
  36  |    1560     |     768     |     640     | 118.3 MB/s 

Completed: 2 Hrs 9 Min 43 Sec.

Best Bang for the Buck: Test 1 with a speed of 118.0 MB/s

     Tunable (md_num_stripes): 1408
     Tunable (md_write_limit): 768
     Tunable (md_sync_window): 512

These settings will consume 126MB of RAM on your hardware.


Unthrottled values for your server came from Test 31 with a speed of 118.3 MB/s

     Tunable (md_num_stripes): 1520
     Tunable (md_write_limit): 768
     Tunable (md_sync_window): 600

These settings will consume 136MB of RAM on your hardware.
This is -422MB less than your current utilization of 558MB.
NOTE: Adding additional drives will increase memory consumption.

 

It looks really odd that all the values are virtually identical. Does this make sense? Is there a potential issue? I wasn't necessarily expecting dramatic variations, but did expect some differences.

 

Also, as a suggestion... it would be great if the tunables text file including the current settings for the 3 variables in it's output so they can be easily referenced again. I wasn't smart enough to write them down before making the change, but would like to have had this documented for reference in case of an issue.

 

That's very different then what most users report with the M1015 cards. It usually is the other way around where as the SAS2LP cards have the slower speeds. Did you buy your M1015's and flash them yourself? You could also put back the SAS2LP cards and try the tunables script again.

 

I believe it is a VERY good idea for this script to BACKUP your disk.cfg file before anything starts considering it does make changes to it.

I believe it is a VERY good idea for this script to BACKUP your disk.cfg file before anything starts considering it does make changes to it.

 

you can restore defaults in the webgui

I believe it is a VERY good idea for this script to BACKUP your disk.cfg file before anything starts considering it does make changes to it.

 

you can restore defaults in the webgui

Not all the settings in the disk.cfg are exposed and restorable in the webgui. Including some that are changed with this script, IIRC.

I didn't see the comments about the script failing with 6.1+, and got the

 

/root/mdcmd: No such file or directory

 

failures so I ^C'd out of the script.  Does anyone know if I need to restore any configuration values due to prematurely exiting out of the script?

 

Thx

I didn't see the comments about the script failing with 6.1+, and got the

 

/root/mdcmd: No such file or directory

 

failures so I ^C'd out of the script.  Does anyone know if I need to restore any configuration values due to prematurely exiting out of the script?

 

Thx

 

Nothing gets changed until the very end when it asks you to change values, and then confirm. You are safe.

 

For what it's worth I re-downloaded the txt file in the first post, and using notepad I did a search and replace of /root/mdcmd to the new path, saved it to my flash drive and then ran the script.

That's very different then what most users report with the M1015 cards. It usually is the other way around where as the SAS2LP cards have the slower speeds. Did you buy your M1015's and flash them yourself? You could also put back the SAS2LP cards and try the tunables script again.

 

I believe it is a VERY good idea for this script to BACKUP your disk.cfg file before anything starts considering it does make changes to it.

 

Lucky me to be running the opposite of everyone else.

 

I did buy them stock, and then flash them with firmware 20.

 

It looks like even with the new settings I am going to be sub-90MB/sec:

 

Total size: 6 TB

Elapsed time: 9 hours, 26 minutes

Current position: 3.22 TB (53.7 %)

Estimated speed: 83.6 MB/sec

Estimated finish: 9 hours, 14 minutes

 

I am confused and somewhat frustrated. Story of my life...

 

I believe it is a VERY good idea for this script to BACKUP your disk.cfg file before anything starts considering it does make changes to it.

 

you can restore defaults in the webgui

Not all the settings in the disk.cfg are exposed and restorable in the webgui. Including some that are changed with this script, IIRC.

 

script changes 3 settings. All 3 are exposed in webgui if you want to manually restore them.

I believe it is a VERY good idea for this script to BACKUP your disk.cfg file before anything starts considering it does make changes to it.

 

you can restore defaults in the webgui

Not all the settings in the disk.cfg are exposed and restorable in the webgui. Including some that are changed with this script, IIRC.

 

script changes 3 settings. All 3 are exposed in webgui if you want to manually restore them.

I think that you manually entered in those values into disk settings.  The script shouldn't touch poll_attributes (used by dynamix for how often to update the temperatures, smart values, etc)

 

The script reports values for num_stripes, write_limit, and sync_window.  The GUI no longer allows you to modify write_limit (although it should properly set it in the disk.cfg file).  That change happened somewhere in the beta series.

 

Your posted picture has dynamix updating the temperatures every 97 minutes

my bad. you're right... scurrying to fix them lol