managed-csi or managed-csi-premium storage class for PVCs?

[dev-samples]

I have deployed k8s 1.22 in azure and I see the following storage classes:

NAME                    PROVISIONER          RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
azurefile               file.csi.azure.com   Delete          Immediate              true                   24d
azurefile-csi           file.csi.azure.com   Delete          Immediate              true                   45d
azurefile-csi-premium   file.csi.azure.com   Delete          Immediate              true                   45d
azurefile-premium       file.csi.azure.com   Delete          Immediate              true                   24d
default (default)       disk.csi.azure.com   Delete          WaitForFirstConsumer   true                   45d
managed                 disk.csi.azure.com   Delete          WaitForFirstConsumer   true                   24d
managed-csi             disk.csi.azure.com   Delete          WaitForFirstConsumer   true                   45d
managed-csi-premium     disk.csi.azure.com   Delete          WaitForFirstConsumer   true                   45d
managed-premium         disk.csi.azure.com   Delete          WaitForFirstConsumer   true                   24d

I am trying to decide which storage class to use for my CI/jenkins containers (running intensive IO disk operations, lots of read/writes of small files).

I don't need to be able to resize existing disks.

Based on:
https://docs.microsoft.com/en-us/azure/aks/azure-disk-csi#dynamically-create-azure-disk-pvs-by-using-the-built-in-storage-classes

Looks like the candidates are:

• managed-csi: Uses Azure Standard SSD locally redundant storage (LRS) to create a managed disk.
• managed-csi-premium: Uses Azure Premium LRS to create a managed disk.

and that both are SSD.

Does selecting managed-csi-premium over managed-csi just mean I get better redundancy of the data? Or are there also better IO performance, attach/detach time for managed-csi-premium?

Also seems to be that managed-premium and managed-csi-premium are identical except for a few parameters? So are managed-premium just kept for backward compatibility?

$ kubectl get sc managed-premium -oyaml
allowVolumeExpansion: true
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  labels:
    addonmanager.kubernetes.io/mode: EnsureExists
    kubernetes.io/cluster-service: "true"
  name: managed-premium
parameters:
  cachingmode: ReadOnly
  kind: Managed
  storageaccounttype: Premium_LRS
provisioner: disk.csi.azure.com
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer

$ kubectl  get sc managed-csi-premium -oyaml
allowVolumeExpansion: true
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  labels:
    addonmanager.kubernetes.io/mode: EnsureExists
    kubernetes.io/cluster-service: "true"
  name: managed-csi-premium
parameters:
  skuname: Premium_LRS
provisioner: disk.csi.azure.com
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer