Know your gear
HPE 3PAR Priority Optimization software enables service levels for applications and workloads as business requirements dictate, enabling administrators to provision storage performance in a manner similar to provisioning storage capacity. This allows the creation of differing service levels to protect mission-critical applications in enterprise environments by assigning a minimum goal for I/O per second and bandwidth, and by assigning a latency goal so that performance for a specific tenant or application is assured. It is also possible to assign maximum performance limits on workloads with lower service-level requirements to make sure that high-priority applications receive the resources they need to meet service levels.
Priority Optimization feature and industries leading "Latency goal" feature that enables the storage administrator to set SLAs as low as 500 µs for volumes residing on SSD storage. It also makes it possible to configure service-level objectives in terms of KB/s and I/O bandwidth on a virtual volume set (VVset) or between different virtual domains. 3 All host I/Os on the VVset are monitored and measured against the defined service-level objective. HPE 3PAR Priority Optimization control is implemented within the HPE 3PAR StoreServ Storage system and can be modified in real time. No host agents are required, and physical partitioning of resources within the storage array is not necessary
Priority Optimization feature and industries leading "Latency goal" feature that enables the storage administrator to set SLAs as low as 500 µs for volumes residing on SSD storage. It also makes it possible to configure service-level objectives in terms of KB/s and I/O bandwidth on a virtual volume set (VVset) or between different virtual domains. 3 All host I/Os on the VVset are monitored and measured against the defined service-level objective. HPE 3PAR Priority Optimization control is implemented within the HPE 3PAR StoreServ Storage system and can be modified in real time. No host agents are required, and physical partitioning of resources within the storage array is not necessary