Azure Files uses file shares as the unit of performance. Unlike Blob/Table storage, partitioning isn't controlled via naming — performance depends on share size, tier, protocol, and IOPS/throughput limits. This simulator helps you model whether your share configuration meets workload needs.
⚙️ Configuration
500,000
📊 Results Summary
-
Total Provisioned IOPS
-
Total Provisioned Throughput
-
IOPS Utilization
-
Throughput Utilization
📏 Capacity & Limits Gauges
📈 Per-Share Load Distribution
Files, IOPS, and throughput allocated per share
🌡️ IOPS per Share vs. Limit
💡 Recommendations
📚 Azure Files Performance Tiers
Azure Files limits are per-share, based on tier and provisioned size:
| Tier | Baseline IOPS | IOPS Formula | Max Throughput | Max Share Size |
|---|---|---|---|---|
| Premium (SSD) | 3,000 | 3,000 + 1 × provisioned GiB | ~100 MiB/s + 0.06 × GiB | 100 TiB |
| Transaction Optimized | 10,000 | Up to 10,000 | Up to 300 MiB/s | 100 TiB |
| Cool | 10,000 | Up to 10,000 | Up to 300 MiB/s | 100 TiB |