RAID 0 for development [closed]

Question

Closed. This question needs to be more focused. It is not currently accepting answers.

---

Want to improve this question? Update the question so it focuses on one problem only by editing this post.

Closed last month.

Improve this question

in your experiences does of real world testing of RAID5 come "close" or "far" behind RAID0 in terms of performance as the underlying storage for a heavy write OLTP workload? Please for the sake of the question ignore any concerns of the usage RAID0 because it lacks durability, as this is out of the scope of the question.

It can be assumed the environment is virtualized in VMWare, the storage median is SAS SSD, the DBMS SQL Server 2017, the OS for the VM is Ubuntu, there is high bandwidth between storage and guest vm 10Gbps for network and 12Gbps for storage.

Thanks you

Answer 1

> is this the best approach for performance?

That is at the same time too broad a question (i.e. will be very opinion based) and to narrow (other people looking for advice are unlikely to have that same config)

> Please remember downtime is acceptable for some servers at a time in the case of a drive failure because this is not production workloads

Are you absolutely 100% sure that this is acceptable? I would want it signed-off in triplicate from the very top because if one bad day you have two drive failures so two of those four RAID0 pods are out of action, you might have an angry manager breathing down your neck wanting to know why half the dev team are out of action (or at least experiencing delays) for how-ever long your time to restore is… To dev managers, dev workloads (and QA workloads) are production workloads. And to get it signed off you are going to need more information, for a start a pessimistic ("realistic worst case") idea of what the restore-to-100% time might be.