Portworx Documentation has moved to https://docs.portworx.com

Portworx Enterprise version 2.13 has reached end of life and end of extended maintenance. Refer to the release support policy doc here.
Upgrade to the latest version of Portworx Enterprise for continued support. Documentation for the latest version of Portworx Enterprise can be found here.

---

Portworx volumes on Kubernetes can use different IO profiles to optimize the Portworx volumes’ performance for specific use-cases. For information about what IO profiles are, as well as the different profiles available, see the IO profiles concept section.

Manually configure IO profiles

You can direct a group of volumes to use a specific IO profile by defining it at the storageClass level and referencing that storageClass in your PVCs:

1. Create and configure a storageClass as desired. Add the parameters.io_profile field with the IO profile you want to specify:

   kind: StorageClass
   apiVersion: storage.k8s.io/v1
   metadata:
     name: portworx-io-profile
   provisioner: kubernetes.io/portworx-volume
   parameters:
   repl: "2"
   io_profile: "db_remote"

2. In your PVCs, reference the storageClass you just created to apply your IO profile to volumes:

   kind: PersistentVolumeClaim
   apiVersion: v1
   metadata:
     name: px-db-remote-pvc
     annotations:
       volume.beta.kubernetes.io/storage-class: portworx-io-profile
   spec:
     accessModes:
       - ReadWriteOnce
     resources:
       requests:
         storage: 10Gi

Related topics

• Performance optimization options in the IO path

---