Skip to main content
NetApp Knowledge Base

Can I modify the IOPS and throughput for GP3 disks after the aggregate has been created in BlueXP?

Views:
196
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
perf
Last Updated:
4/5/2024, 7:08:24 PM

Applies to

  • Cloud Volumes ONTAP (CVO)
  • Amazon Web Services (AWS)

Answer

  • Yes, however the IOPS and throughput changes need to be made from the AWS EC2 console instead of BlueXP
  • Alternatively, you can create a new GP3 aggregate in BlueXP with your preferred IOPS and throughput, volume move any volumes to the new aggregate, and destroy the original aggregate in BlueXP

Additional Information

Details about GP3 aggregates created in BlueXP:

General Purpose SSD (gp3) disks are the lowest-cost SSDs that balance cost and performance for a broad range of workloads. Performance is defined in terms of IOPS and throughput. gp3 disks are supported with Cloud Volumes ONTAP 9.7 and later. When you select a gp3 disk, BlueXP fills in default IOPS and throughput values that provide performance that is equivalent to a gp2 disk based on the selected disk size. You can increase the values to get better performance at a higher cost, but we do not support lower values because it can result in inferior performance.

 

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.