Hi all,
We have a reasonable amount of NL storage free, however we take a hit on the physical disk IO quite consistently. At the moment the CPG is set to use RAID 6 (4+2).
Is there any merit in changing the data number up for an increase in performance (or even changing the RAID type all together)?
Any thoughts?
Changing RAID config on CPG
- Richard Siemers
- Site Admin
- Posts: 1333
- Joined: Tue Aug 18, 2009 10:35 pm
- Location: Dallas, Texas
Re: Changing RAID config on CPG
What size drives are these? How are your current rebuild times?
Richard Siemers
The views and opinions expressed are my own and do not necessarily reflect those of my employer.
The views and opinions expressed are my own and do not necessarily reflect those of my employer.
-
- Posts: 17
- Joined: Mon Oct 14, 2013 3:40 am
Re: Changing RAID config on CPG
Hi Richard,
That's a good question, we've only had the array around 1yr and have been lucky enough not to endure any failures yet (touch wood).
At this stage there are 24 x 2TB drives in a single cage.
Thanks.
That's a good question, we've only had the array around 1yr and have been lucky enough not to endure any failures yet (touch wood).
At this stage there are 24 x 2TB drives in a single cage.
Thanks.
-
- Posts: 71
- Joined: Tue May 27, 2014 11:23 am
Re: Changing RAID config on CPG
I wouldn't bank on getting a lot of performance from your NL disks. When you are designing a system HP best practice is that you don't even count NL disks IOPs when trying to meet your IOPs target. Do you have another tier of storage in your system and AO?
Twitter @d8taDude
Re: Changing RAID config on CPG
Well if you want performance out of them and since they're nearline, why not consider converting them to Raid 1 ?
- Richard Siemers
- Site Admin
- Posts: 1333
- Joined: Tue Aug 18, 2009 10:35 pm
- Location: Dallas, Texas
Re: Changing RAID config on CPG
We have a 7200 with 24x 3TB drives, but running at Raid6, 6+2.
It was intended for deep capacity and low performance. The app that uses it does mostly sequential reads and writes, and it suits our needs well.
We go out of our way to make sure random workloads get parked on SAS/FC/SSD disk.
It was intended for deep capacity and low performance. The app that uses it does mostly sequential reads and writes, and it suits our needs well.
We go out of our way to make sure random workloads get parked on SAS/FC/SSD disk.
Richard Siemers
The views and opinions expressed are my own and do not necessarily reflect those of my employer.
The views and opinions expressed are my own and do not necessarily reflect those of my employer.