QoS is a means to ensure specific performance levels for applications and workloads. There are two ways to accomplish this:
1. Ability to set limitations to avoid unwanted behavior from non-critical clients/hosts.
2. Ability to set guarantees to ensure service levels for mission-critical clients/hosts.
Pivot3 Acuity supports the second method through pre-defined performance policies per volume. These policies can be changed manually on-the-fly or automatically by configuring and assigning schedules.
The pre-defined service levels govern how the QoS engine treats the targets in order to maintain Mission Critical performance, then Business Critical performance and then Non-critical performance.
The pre-defined service levels also govern how the read-warm cache is getting populated:
Policy 1 – Mission Critical – 1 hit per 1MB Region
Policy 2 – Business Critical – 4 hits per 1MB Region
Policy 3 – Business Critical – 16 hits per 1MB Region
Policy 4 – Non-Critical – read-warm disabled
Policy 5 – Non-Critical – read-warm disabled
The pre-defined service levels also govern how read-ahead is used:
Policy 1 – Mission Critical – enabled
Policy 2 – Business Critical – enabled
Policy 3 – Business Critical – enabled
Policy 4 – Non-Critical – read-ahead disabled
Policy 5 – Non-Critical – read-ahead disabled