Performance service levels in Keystone
Suggest changes
PDFs
Keystone STaaS offers data storage capacity at pre-defined performance service levels. Each volume managed by Keystone services is associated with a performance service level.
A subscription can have multiple rate plans and each rate plan corresponds to a performance service level. Each rate plan has a committed capacity per performance service level.
A performance service level can have multiple instances, with each instance representing a separate storage array assigned to that performance service level in the customer's environment. Each performance service level is defined by input/output operations per second (IOPS), throughput (GBps), and latency (ms), with these metrics measured and applied per performance service level instance.
You select performance service levels based on your storage environment, and storage and consumption needs. The base performance service levels are available for you by default. Specific performance service levels are additionally available, if you have opted for add-on services.
|
A detailed service description for NetApp Keystone STaaS performance service levels is available here. |
The base performance service levels for the supported storage types, unified, block-optimized, object, and cloud services are described in the following sections:
Performance service levels for unified storage
Supported protocols: FC, iSCSI, NFS, NFSv4/RDMA, NVMe/FC, NVMe/TCP, SMB, S3
Performance service level |
Extreme |
Premium |
Standard |
Value |
Sample workload types |
AI/ML, HPC, InMem DB |
Analytics, EDA, OLTP |
OLAP, IoT, Containers |
Backup, Archive |
Maximum IOPS1 |
1M |
550K |
500K |
NA |
Maximum GBps |
40 |
20 |
20 |
NA |
Target 90th percentile latency |
<=1 ms |
<=1 ms |
<=4 ms |
>4 ms |
Minimum committed capacity |
50 TiB |
50 TiB |
100 TiB |
100 TiB |
Incremental committed capacity increase |
25TiB |
|||
Committed and metered capacity type |
Logical or physical |
|||
Performance service levels for block-optimized storage
Supported protocols: NVMe/TCP, NVMe/FC, FC, iSCSI
Performance service level |
Extreme |
Premium |
Sample workload types |
SAP HANA, Oracle, MS SQL Server, EPIC |
|
Maximum IOPS1 |
850K |
450K |
Maximum GBps |
65 |
25 |
Target 90th percentile latency |
<=1 ms |
<=1 ms |
Minimum committed capacity |
50 TiB |
50 TiB |
Incremental committed capacity increase |
25TiB |
|
Committed and metered capacity type |
Logical or physical |
|
|
1Mutually exclusive targets. Actual performance may differ based on various factors, including the operating system version, hardware, workload type, and number of concurrent operations. |
More on performance service levels for unified and block-optimized storage
The base performance service level metrics depend on the following conditions:
-
The performance service levels support ONTAP 9.8 and later.
-
For unified storage,
-
IOPS: For ONTAP 9.16.1 with NFS, each performance level instance supports random access with a 70% read and 30% write ratio, an 8 KB block size, and a latency of 1 ms (4 ms for Standard).
-
Throughput: For ONTAP 9.16.1 with NFS, each performance level instance supports sequential access with 100% read and a 32 KB block size.
-
-
For block-optimized storage,
-
IOPS: For ONTAP 9.16.1 with FCP, each performance level instance supports random access with a 70% read and 30% write ratio, an 8 KB block size, and a latency of 1 ms.
-
Throughput: For ONTAP 9.16.1 with FCP, each performance level instance supports sequential access with 100% read and a 64 KB block size.
-
-
Latency does not include the following:
-
application or host latency
-
customer network latency to or from the controller ports
-
overheads associated with the data transfer to the object store in case of FabricPool
-
-
Latency values are not applicable to MetroCluster write operations. These write operations are dependent on the distance of remote systems.
-
Expected IOPS is targeted for FabricPool only if the tiering policy is set to "none" and no blocks are in the cloud. Expected IOPS is targeted for volumes that are not in a SnapMirror synchronous relationship.
Performance service levels for object storage
Supported protocol: S3
Performance service level |
Standard |
Value |
Minimum committed capacity per order |
200 TiB |
500 TiB |
Incremental committed capacity increase |
25 TiB |
100 TiB |
Committed and metered capacity type |
Physical |
|
Cloud storage
Supported protocols: NFS, CIFS, iSCSI, and S3 (AWS and Azure only)
Performance service level |
Cloud Volumes ONTAP |
Minimum committed capacity per order |
4 TiB |
Incremental committed capacity increase |
1 TiB |
Committed and metered capacity type |
Logical |
|
|
|
Related information