Interesting you mention the raid.reconstruct.perf_impact setting - I was a little confused about its real meaning...
I thought (as you mentioned) that setting it to 'high' would increase the reconstruct speed. I then used the filerview web interface to go in and change the raid reconstruct speed to 'high' and it actually set this value to 'low' - the web tool seems to set it to the inverse of what you'd expect. (setting 'low' on the web interface sets this option to 'high' etc.)
So I was a little curious as to if the setting had a different meaning than the one you (and I) initially thought it meant. (eg: perhaps it's meaning impact on reconstruct speed rather than system performance, so 'low' means the least affect on reconstruct speed and therefore the most impact on system performance) I left it at 'low' since I figured the web interface probably knew the meaning of the option a little more than I did...
Simon.
-----Original Message----- From: Hill, Aaron [mailto:aaron.hill@cba.com.au] Sent: Friday, September 10, 2004 1:53 AM To: Simon Ferrett; toasters@mathworks.com Subject: RE: New Simplified Monitoring Tool
Simon, I don't know if you can directly increase the no. of simultaneous reconstructs. However, you may be able to improve the speed marginally by using the raid.reconstruct.perf_impact option and setting to high. However, if your cpu's are already maxxed it probably won't make a lick of difference.
---
This email message and any attachments are for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient or his/her representative, please contact the sender by reply email and destroy all copies of the original message.