Skip to content

Commit 65dde2a

Browse files
Merge pull request #250943 from khdownie/patch-1
Update analyze-files-metrics.md
2 parents 99eab69 + 3adde95 commit 65dde2a

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

articles/storage/files/analyze-files-metrics.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -298,8 +298,6 @@ Because Azure Premium file shares are billed on a provisioned model in which eac
298298

299299
With Azure Premium file shares, you can use **Transactions by Max IOPS** and **Bandwidth by Max MiB/s** metrics to display what your workload is achieving at peak times. Using these metrics to analyze your workload will help you understand true capability at scale, as well as establish a baseline to understand the impact of more throughput and IOPS so you can optimally provision your Azure Premium file share.
300300

301-
These metrics are calculated by omitting the maximum value over 60 seconds. For example, if your workload generated 1 IOPS for 59 seconds and then 1,000 IOPS on the 60th second, then **Transaction by Max IOPS** would display 1 k/s because that was the peak within that 1 minute interval.
302-
303301
The following chart shows a workload that generated 2.63 million transactions over 1 hour. When 2.63 million transactions is divided by 3,600 seconds, we get an average of 730 IOPS.
304302

305303
:::image type="content" source="media/analyze-files-metrics/transactions-sum.png" alt-text="Screenshot showing the transactions generated by a workload over one hour." lightbox="media/analyze-files-metrics/transactions-sum.png" border="false":::

0 commit comments

Comments
 (0)