Adventures in Motherboard Raid (it's bad)

Summary

The video script is an in-depth exploration of RAID configurations on motherboards, focusing on the challenges and potential of using RAID for performance enhancement. The narrator, driven by a passion for technology, warns against common pitfalls and advocates for a thorough understanding of RAID's benefits and drawbacks. The discussion covers various RAID levels, including RAID 0, RAID 1, and RAID 10, across both Intel and AMD platforms. It highlights the importance of proper driver support, the impact of TRIM on SSD performance, and the potential of alternative solutions like PrimoCache and Intel's VROC. The script serves as a comprehensive guide for those considering RAID for their storage needs.

Takeaways

• 🚫 The script advises against using motherboard RAID due to complications and recommends understanding the specific issues before implementing RAID.
• 💾 RAID configurations can offer performance boosts or data resiliency, but they require careful setup and management, unlike simply adding memory.
• 🖥️ Apple's use of RAID in some Mac Pros for performance, without redundancy, highlights the potential benefits of RAID for specific use cases.
• 📊 RAID performance is not just about throughput but also latency, which can be affected by how well the RAID driver manages multiple drives.
• 🛠️ Intel's VROC system is praised for its engineering and performance when it works correctly, but it has faced issues with implementation and marketing.
• 💔 AMD's RAID implementation has been found to underperform, with problems such as not effectively using all drives for read operations and issues with TRIM support.
• 🔄 The script suggests that for non-bootable volumes, Windows' built-in RAID options or Linux's software RAID can be more effective than using AMD's RAID drivers.
• 💾 Enterprise SSDs like Intel P4500 are highlighted as being better suited for servers rather than workstations or gaming, despite their high performance.
• 🔧 The importance of checking cables and SATA ports is emphasized due to their potential impact on RAID array performance.
• ⏱️ The script discusses the impact of caching settings on RAID performance, noting that conservative settings can protect data but limit speed.

Q & A

What is RAID and what does it stand for?

RAID stands for Redundant Array of Inexpensive Disks (or Drives, as the term 'disks' has been replaced with 'drives' to include NVMe drives). It is a technology that combines multiple storage devices to provide either a performance boost or data resiliency.

Why does the speaker suggest avoiding using RAID on the motherboard?

The speaker suggests avoiding RAID on the motherboard because it can be a mess and not worth the time and headache. They imply that there are often better alternatives and that motherboard RAID can lead to various issues without significant benefits.

What are the two main benefits of using RAID configurations?

The two main benefits of using RAID configurations are increased performance and data resiliency. Performance is achieved by combining multiple drives to increase throughput, while data resiliency ensures that if one drive fails, the data is still accessible from the other drives in the array.

What is the difference between Intel VRoc and AMD RAID according to the script?

Intel VRoc is a technology that works well with specific Intel platforms, offering hardware and software engineering that accelerates RAID operations. AMD RAID, on the other hand, is described as less efficient, with performance issues and problems with TRIM support, making it less desirable for use except for specific bootable configurations.

Why might someone choose to use RAID 0 with NVMe drives?

Someone might choose to use RAID 0 with NVMe drives for the purpose of achieving maximum performance by striping data across multiple drives. However, this configuration offers no data redundancy, so if one drive fails, all data is lost.

What is the issue with using SATA RAID on AMD systems as described in the script?

The script describes issues with SATA RAID on AMD systems, including not achieving expected read IOPS and problems with error handling that can lead to slower performance without clear error reporting.

What is the role of TRIM in SSDs and why is it important for RAID configurations?

TRIM is a command that allows an operating system to inform an SSD which blocks of data are no longer in use and can be wiped internally. This is important for RAID configurations, especially with SSDs, to maintain write performance and prevent the drives from becoming slow over time due to garbage collection issues.

What alternative to RAID does the speaker suggest for improving performance?

The speaker suggests using caching solutions like PrimoCache or Intel Optane as alternatives to RAID for improving performance. These technologies can boost IOPS and reduce latency without the complexity and potential issues of RAID configurations.

What is the speaker's opinion on using RAID for boot volumes?

The speaker believes that RAID can be used for boot volumes, especially in configurations that mirror or stripe data for performance. However, they also note that TRIM support is crucial for maintaining performance with SSDs in these setups.

What is the significance of the Intel performance table mentioned in the script?

The Intel performance table is significant because it provides expected performance metrics for different RAID configurations, which can be used as a benchmark to compare the actual performance of RAID setups. The script mentions that real-world testing should align with these expectations, highlighting the importance of accurate documentation in RAID technology.