We are using HP Vertica database 7.2 community version. 300GB of data on one node. Thats a small amount of data.

HP officially recommends RAID 1+0. https://community.dev.hpe.com/t5/Vertica-Knowledge-Base/RAID-Storage-for-HPE-Vertica/ta-p/234225

But I do not envision a problem with write performance which is the point of RAID 0. I am not planning to load, insert or write large amounts of data. I am planning to query large amounts of data, but not write a lot. It seems to me that RAID 1 is sufficient.

Is there anything wrong with using RAID 1 instead of 1+0?

  • 1
    Striping (RAID 0) improves I/O performance in general, not just writes. – mustaccio Aug 8 '16 at 18:18
  • You need to better analyze the amount of data used per query, vertica does an efficient job at reading only what's needed so you need to understand how much are you planning to read per query - this will give you the impact on query times. also note that a single disk will have impact on the query concurrency. – cohenjo Aug 8 '16 at 19:46
  • Closing this as opinion based, but if you want my opinion go with the best practices unless your benchmarks prove otherwise. – Tom V - try topanswers.xyz Aug 9 '16 at 18:42

This is a pretty open ended question and you might want to just test it yourself and see. It depends on how you query and write the data. This will determine how many IOPS you need at peak use, which if you want to ensure you'd figure out by testing then deciding.

However if that is not an option, do you have hundreds of gigs of RAM? Some systems do. If so, perhaps your read/write patterns will hit RAM and Disk IO won't matter. Are you using SSDs or magnetic disks? SSDs have a much higher disk IO and IOPS than traditional spinning media so the write penalty might not even be noticeable.

Really not sure how much more to add here, it'll come down to your testing results and IOPS needs.

| improve this answer | |

Not the answer you're looking for? Browse other questions tagged or ask your own question.