The CX based defrag could cause a performance impact if set to high priority. If set to low there should be only very minimal impact and not noticable. I don't recall doing this on Celerra used raid groups, but did this all the time on server used raid groups with no issues. If concerned about performance, just set the priority to low.
I wouldn't worry too much about the "big performance hit". We defrag all the time and no user ever reported any performance issues and believe me they jump at this any time they can. I am willing to say that the defragging is not noticeable when performed with low or medium priority.
kensagle
59 Posts
0
June 1st, 2010 08:00
The CX based defrag could cause a performance impact if set to high priority. If set to low there should be only very minimal impact and not noticable. I don't recall doing this on Celerra used raid groups, but did this all the time on server used raid groups with no issues. If concerned about performance, just set the priority to low.
Sagle
dynamox
9 Legend
•
20.4K Posts
0
June 1st, 2010 11:00
YMMV ..i’ve worked in shops where jump in response time from 5ms to 20ms was generating phone calls to the help desk.
Uwe-Ud0Mk
37 Posts
0
June 1st, 2010 11:00
I wouldn't worry too much about the "big performance hit". We defrag all the time and no user ever reported any performance issues and believe me they jump at this any time they can. I am willing to say that the defragging is not noticeable when performed with low or medium priority.