update testing values

Author: b-ahibbard

articles/azure-netapp-files/performance-impact-kerberos.md

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: conceptual
-ms.date: 06/25/2021
+ms.date: 07/22/2022
 ms.author: anfdocs
 ---
 # Performance impact of Kerberos on Azure NetApp Files NFSv4.1 volumes
@@ -48,60 +48,18 @@ There are two areas of focus: light load and upper limit. The following lists de
 
 **Performance impact of krb5:**
 
-<!-- 
-Average IOPS: ~11351 / -53%
-Average throughput: ~355 MB/s / -53%
-Average latency: ~3.2 ms / +540%
-
-
-* Low concurrency (r/w):
-    * Sequential latency increased 0.3 ms.
-    * Random I/O latency increased 0.2 ms.
-    * Metadata I/O latency increased 0.2 ms.
-* High concurrency (r/w): 
-    * Maximum sequential throughput was unimpacted by krb5.
-    * Maximum random I/O decreased by 30% for pure read workloads with the overall impact dropping to zero as the workload shifts to pure write. 
-    * Maximum metadata workload decreased 30%.
--->
+* Average IOPS decreased by 53%
+* Average throughput decreased by 53% 
+* Average latency increased by 3.2 ms
 
 **Performance impact of krb5i:**
 
-<!-- 
-Average IOPS: ~10856 / -55%
-Average throughput: ~338 MB/s / -55%
-Average latency: ~1.1 ms / +120%
-
-* Low concurrency (r/w):
-    * Sequential latency increased 0.5 ms.
-    * Random I/O latency increased 0.2 ms.
-    * Metadata I/O latency increased 0.2 ms.
-* High concurrency (r/w): 
-    * Maximum sequential throughput decreased by 70% overall regardless of the workload mixture.
-    * Maximum random I/O decreased by 50% for pure read workloads with the overall impact decreasing to 25% as the workload shifts to pure write. 
-    * Maximum metadata workload decreased 30%.
--->
-
 * Average IOPS decreased by 55%
 * Average throughput decreased by 55% 
 * Average latency increased by 0.6 ms
 
 **Performance impact of krb5p:**
 
-<!-- 
-Average IOPS: ~5579 / -77%
-Average throughput: ~174 MB/s / -77%
-Average latency: ~2.1 ms / +320%
-
-* Low concurrency (r/w):
-    * Sequential latency increased 0.8 ms.
-    * Random I/O latency increased 0.2 ms.
-    * Metadata I/O latency increased 0.2 ms.
-* High concurrency (r/w): 
-    * Maximum sequential throughput decreased by 85% overall regardless of the workload mixture. 
-    * Maximum random I/O decreased by 65% for pure read workloads with the overall impact decreasing to 43% as the workload shifts to pure write. 
-    * Maximum metadata workload decreased 30%.
--->
-
 * Average IOPS decreased by 77%
 * Average throughput decreased by 77% 
 * Average latency increased by 1.6 ms