About striping file systems
You can obtain huge performance benefits by striping (RAID-0) using software-defined storage (SDS). You achieve performance benefits regardless of the choice of LUN configuration in your storage hardware. Striping is useful if you need large amounts of data that is written to or read from physical disks, and consistent performance is important. SDS striping is a good practice for all Access Appliance use cases and workloads.
Veritas strongly recommends that you create striped file systems when creating your file system for the following reasons:
Maximize the I/O performance.
Proportion the I/O bandwidth available from the storage layer.
Balance the I/O load evenly across multi-user applications running on multiple nodes in the cluster.
However there are also pitfalls to avoid.
The following information is essential before selecting the disks to include in your striped file system:
Understanding of your hardware environment
Storage capabilities and limitations (bottlenecks)
Choice of LUNs (each LUN, or disk, equates to a column in a SDS-striped volume)
An extreme example might be if one column (equal to one LUN) is composed of only hard disk drives (HDDs) in the storage array. All of the other columns in the same striped volume are composed of only SSDs in the storage array. The overall I/O performance bottlenecks on the single slower HDD LUN.
Understanding the LUN configuration and ensuring that all of the LUNs have an identical configuration is therefore essential for maximizing performance and achieving balanced I/O across all the LUNs.
All 24 LUNs have an identical hardware configuration.
The performance team created a volume with 24 columns to use the entire storage bandwidth in one file system. Veritas does not advise changing the operating system default maximum I/O size of 512 KB. The optimum stripe-unit size is 512 KB.