Your Browser is Out of Date

ShareDemos uses technology that works best in other browsers.
For a full experience use one of the browsers below
Validation Guide—Storage Configuration Best Practices for SAP HANA TDI on Unity XT Systems
SAP HANA host configuration and setup
Host connection using Fibre Channel SAN Host connection using NAS (NFS) SAP HANA capacity requirements Competing workloads

Competing workloads

  • When adding workloads to the Unity XT system, consider the reported CPU utilization rates as well as the capacity and IOPS sizing. Brief spikes of high utilization are normal and expected on any Unity XT system. For information about sustained CPU utilization and recommended operating ranges that influence whether the system can accept additional workloads, see the Dell EMC Unity: Best Practices Guide.

    In highly consolidated environments, SAP HANA competes for storage resources along with other databases and applications. You can use host I/O limits, a quality of service (QoS) feature, to control “noisy neighbors” and protect the SAP HANA production system performance.

    Host I/O limits

    The ability to limit the number of IOPS that the Unity XT system services is known as host I/O limits. Host I/O limits can be applied on LUNs, VMware vStorage VMFS datastores, and their associated snapshots. Use host I/O limits to limit incoming host activity based on IOPS, bandwidth, or both. You can enforce limits on individual resources or share a limit among a set of resources.

    Host I/O limits can be effective in consolidated environments if an overload on the storage resources affects the performance of more critical applications such as SAP HANA production installations. To protect the performance of SAP HANA production systems, consider configuring host I/O limits on LUNs, datastores of applications other than SAP HANA applications, or SAP HANA nonproduction systems to limit the total IOPs or bandwidth.