-
-
unraid-tunables-tester.sh - A New Utility to Optimize unRAID md_* Tunables
I used the unthrottled settings instead of the best bang for your buck. Is there any reason I should switch to the best bang for your buck? I have 12GB of RAM and only use MariaDB, Cache_Dirs, and APCUPSD. I am pretty sure I have more than enough RAM to swing the additional memory consumption. Opinions? Thoughts? 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 | 120.8 MB/s 2 | 1536 | 768 | 640 | 121.4 MB/s 3 | 1664 | 768 | 768 | 121.3 MB/s 4 | 1920 | 896 | 896 | 121.6 MB/s 5 | 2176 | 1024 | 1024 | 121.8 MB/s 6 | 2560 | 1152 | 1152 | 121.9 MB/s 7 | 2816 | 1280 | 1280 | 121.9 MB/s 8 | 3072 | 1408 | 1408 | 122.1 MB/s 9 | 3328 | 1536 | 1536 | 122.1 MB/s 10 | 3584 | 1664 | 1664 | 122.1 MB/s 11 | 3968 | 1792 | 1792 | 122.2 MB/s 12 | 4224 | 1920 | 1920 | 122.1 MB/s 13 | 4480 | 2048 | 2048 | 122.1 MB/s 14 | 4736 | 2176 | 2176 | 122.2 MB/s 15 | 5120 | 2304 | 2304 | 122.1 MB/s 16 | 5376 | 2432 | 2432 | 122.1 MB/s 17 | 5632 | 2560 | 2560 | 122.2 MB/s 18 | 5888 | 2688 | 2688 | 122.0 MB/s 19 | 6144 | 2816 | 2816 | 122.2 MB/s 20 | 6528 | 2944 | 2944 | 122.1 MB/s --- Targeting Fastest Result of md_sync_window 1792 bytes for Final Pass --- --- FULLY AUTOMATIC TEST PASS 2 (Final - 16 Sample Points @ 4min Duration)--- 21 | 3712 | 1672 | 1672 | 122.3 MB/s 22 | 3728 | 1680 | 1680 | 122.1 MB/s 23 | 3744 | 1688 | 1688 | 122.2 MB/s 24 | 3768 | 1696 | 1696 | 122.1 MB/s 25 | 3784 | 1704 | 1704 | 122.3 MB/s 26 | 3800 | 1712 | 1712 | 122.3 MB/s 27 | 3816 | 1720 | 1720 | 122.2 MB/s 28 | 3840 | 1728 | 1728 | 122.2 MB/s 29 | 3856 | 1736 | 1736 | 122.2 MB/s 30 | 3872 | 1744 | 1744 | 122.2 MB/s 31 | 3888 | 1752 | 1752 | 122.3 MB/s 32 | 3904 | 1760 | 1760 | 122.3 MB/s 33 | 3928 | 1768 | 1768 | 122.2 MB/s 34 | 3944 | 1776 | 1776 | 122.1 MB/s 35 | 3960 | 1784 | 1784 | 122.2 MB/s 36 | 3976 | 1792 | 1792 | 122.3 MB/s Completed: 2 Hrs 7 Min 25 Sec. Best Bang for the Buck: Test 1 with a speed of 120.8 MB/s Tunable (md_num_stripes): 1408 Tunable (md_write_limit): 768 Tunable (md_sync_window): 512 These settings will consume 77MB of RAM on your hardware. Unthrottled values for your server came from Test 21 with a speed of 122.3 MB/s Tunable (md_num_stripes): 3712 Tunable (md_write_limit): 1672 Tunable (md_sync_window): 1672 These settings will consume 203MB of RAM on your hardware. This is 126MB more than your current utilization of 77MB. NOTE: Adding additional drives will increase memory consumption. In unRAID, go to Settings > Disk Settings to set your chosen parameter values.
-
LSI Controller FW updates IR/IT modes
Successfully flashed 2 more LSI MegaRAID cards. I am incredibly appreciative of all the hardwork that was done to put this together.
-
How much RAM do you have installed in your unRAID server?
Both my servers run 4GB right now. Once I finally upgrade to v6.0 I will hopefully be swapping to either 8GB or 16GB, depending on pricing.
-
unraid-tunables-tester.sh - A New Utility to Optimize unRAID md_* Tunables
Under what circumstances would we need to run this script again?
-
unraid-tunables-tester.sh - A New Utility to Optimize unRAID md_* Tunables
Well I ran a parity check last night and only saw about a 10 minute improvement. I was really hoping for more. Still ended up taking 9:10 to complete with no errors. Oh well. Must be those 2TB drives.
-
unraid-tunables-tester.sh - A New Utility to Optimize unRAID md_* Tunables
I would definitely like to drop the 2tb drives but considering I probably couldn't sell them for much it wouldn't be cost effective. I would definitely love to get rid of that slow down though. I will have to post up the results of my parity check when I run it tomorrow.
-
unraid-tunables-tester.sh - A New Utility to Optimize unRAID md_* Tunables
Just a thought but what if we created a separate thread to have people post their system specs with the speeds they achieved and their UnRaid version, script version tested, and ultimately the values they used? This might be a good way for people to get an idea of potential parity check speeds with different hardware, especially if they are looking to upgrade or purchase a new system.
-
unraid-tunables-tester.sh - A New Utility to Optimize unRAID md_* Tunables
If the difference is only around a minute then I should probably just stick with the best bang for the buck settings. I will be excited to see the results of my parity check. Maybe it will actually be able to finish before I wake up now. Also it wasn't that I was complaining about the speeds because I see there are definitely others who are having some serious speed issues. It was more I was hoping to pull in the 130-140 range. However if my parity check decreases in time safely then I will be happy and maybe when I pull the 2tb drives out the speeds will increase. Now to run it on my other server that has all 3tb drives and see how that turns out.
-
unraid-tunables-tester.sh - A New Utility to Optimize unRAID md_* Tunables
Well I was hoping it would be a bit better than this but I guess it's not too bad. Any reason I shouldn't consider the slightly higher speed of run 23? Also any thoughts on what i could do to increase this value? I am assuming my 4x 2tb wd green and my 2x 2tb 5900rpm seagates are keeping the speeds down? 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 | 120.5 MB/s 2 | 1536 | 768 | 640 | 120.8 MB/s 3 | 1664 | 768 | 768 | 121.2 MB/s 4 | 1920 | 896 | 896 | 121.4 MB/s 5 | 2176 | 1024 | 1024 | 121.6 MB/s 6 | 2560 | 1152 | 1152 | 121.7 MB/s 7 | 2816 | 1280 | 1280 | 121.9 MB/s 8 | 3072 | 1408 | 1408 | 121.8 MB/s 9 | 3328 | 1536 | 1536 | 121.9 MB/s 10 | 3584 | 1664 | 1664 | 121.9 MB/s 11 | 3968 | 1792 | 1792 | 121.9 MB/s 12 | 4224 | 1920 | 1920 | 121.8 MB/s 13 | 4480 | 2048 | 2048 | 121.8 MB/s 14 | 4736 | 2176 | 2176 | 121.8 MB/s 15 | 5120 | 2304 | 2304 | 121.9 MB/s 16 | 5376 | 2432 | 2432 | 121.9 MB/s 17 | 5632 | 2560 | 2560 | 121.9 MB/s 18 | 5888 | 2688 | 2688 | 121.9 MB/s 19 | 6144 | 2816 | 2816 | 121.9 MB/s 20 | 6528 | 2944 | 2944 | 121.9 MB/s --- Targeting Fastest Result of md_sync_window 1280 bytes for Final Pass --- --- FULLY AUTOMATIC TEST PASS 2 (Final - 16 Sample Points @ 4min Duration)--- 21 | 2576 | 1160 | 1160 | 121.9 MB/s 22 | 2592 | 1168 | 1168 | 121.9 MB/s 23 | 2608 | 1176 | 1176 | 122.0 MB/s 24 | 2624 | 1184 | 1184 | 121.9 MB/s 25 | 2648 | 1192 | 1192 | 121.8 MB/s 26 | 2664 | 1200 | 1200 | 121.9 MB/s 27 | 2680 | 1208 | 1208 | 122.0 MB/s 28 | 2696 | 1216 | 1216 | 122.0 MB/s 29 | 2720 | 1224 | 1224 | 122.0 MB/s 30 | 2736 | 1232 | 1232 | 122.0 MB/s 31 | 2752 | 1240 | 1240 | 122.0 MB/s 32 | 2768 | 1248 | 1248 | 121.9 MB/s 33 | 2784 | 1256 | 1256 | 122.0 MB/s 34 | 2808 | 1264 | 1264 | 122.0 MB/s 35 | 2824 | 1272 | 1272 | 122.0 MB/s 36 | 2840 | 1280 | 1280 | 121.9 MB/s Completed: 2 Hrs 7 Min 2 Sec. Best Bang for the Buck: Test 1 with a speed of 120.5 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 23 with a speed of 122.0 MB/s Tunable (md_num_stripes): 2608 Tunable (md_write_limit): 1176 Tunable (md_sync_window): 1176 These settings will consume 101MB of RAM on your hardware. This is 51MB more 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.
-
webGui on github
That's awesome to hear Tom. Thanks for everything you do.
-
webGui on github
I understand they are plug-ins. I was merely stating it would be awesome if they were ported over, especially since Simple Features was the basis for this GUI. Also I recognize this is not a trivial undertaking. I am a professional software tester and completely understand the time and energy that must be put into these things. I was just trying to offer suggestions of features that I thought would be nice to have.
-
unraid-tunables-tester.sh - A New Utility to Optimize unRAID md_* Tunables
I am hoping to run this tonight now that I have upgraded to 5.0. I can post up my results if there is interest. Fingers crossed on a faster parity check than what I get now.
-
webGui on github
I would also love to see the Stats Page and also a way to run Smart Reports from the GUI like Simple Features had. Also, this may have been suggested before, I would love to see the Array drives appearing at the top with the Flash and Cache drives at the bottom of the main menu. After all I look at my Array drives way more than the other two. Now that this is an official GUI is there any chance of integrating with Joe L. 's preclear script. I realize this would involve working with Joe and this may not be a possibility but it would be pretty cool. Even if it just reported the status of the preclear as it was underway.
-
unraid-tunables-tester.sh - A New Utility to Optimize unRAID md_* Tunables
Now that the time needed to run this script has decreased you should probably update the original posts to reflect thedecrease in time.
-
unraid-tunables-tester.sh - A New Utility to Optimize unRAID md_* Tunables
Everyone keeps talking about watching video during parity checks and I have seen numerous complaints about how this is a problem. On my stock settings I can't even watch a video during a parity check. I have always accepted that as a necessary evil during parity checks. If I can shave time off my parity check and do it safely using this utility then that is fantastic and I am all for it. Right now a parity check takes me about 9.5 hours give or take. One question though, would this have any effect on the rebuild speed if a disk fails?
mobias1313
Members
-
Joined
-
Last visited