Optimize Azure Storage Accounts
Azure Storage Accounts offer versatile features to support a variety of workloads. By applying cost-effective strategies and leveraging the right configuration, you can optimize performance and minimize expenses.
Talk to an Azure expert! Email us or schedule a 30-minute consultation and let's optimize your Azure environment together!
Stay ahead with actionable insights for Azure optimization. Subscribe to updates and unlock the full potential of Azure!
Cost Optimization Recommendations
General-Purpose v2 Storage Accounts
Consider upgrading your storage accounts from General-purpose v1 (GPv1) to General-purpose v2 (GPv2) to unlock the latest features and storage cost savings.
Storage V2 Features
- Access tiers: Hot, Cool, Cold, and Archive.
- Lifecycle management for automatic data movement between tiers.
- Competitive pricing for storage capacity and transactions.
- Up to 30% lower storage costs compared to GPv1.
- Increased flexibility to optimize costs based on data access patterns.
- Learn more about GPv2
The table below highlights the cost differences between storage accounts, along with potential savings based on data storage costs. However, the decision to upgrade depends on the volume and type of storage transactions being performed.
Storage Cost Comparison (Australia East Region)
Account Type | Redundancy | Storage Cost (Per GB) | Savings (%) |
---|---|---|---|
General Purpose v1 (GPv1) | Locally Redundant Storage (LRS) | US$0.03 | N/A |
General Purpose v2 (GPv2) - Hot Tier | Locally Redundant Storage (LRS) | US$0.02 | ~33% |
Note: Prices vary based on Azure region. Review the Azure pricing calculator for up-to-date cost estimations.
Transaction Cost Comparison (Australia East Region)
Account Type | Transaction Type | Cost Per 10,000 Operations |
---|---|---|
General Purpose v1 (GPv1) | Write, Read, List, Create, Other | US$0.00036 |
General Purpose v2 (GPv2) - Hot Tier | Write, Create | US$0.055 |
General Purpose v2 (GPv2) - Hot Tier | Read, Other | US$0.004 |
-
Storage Savings:
GPv2 offers a 33.33% savings on storage costs per GB compared to GPv1. This makes it an ideal choice for large-scale data storage where the volume of data is significant. -
Transaction Costs:
- For write and create operations, GPv2 costs significantly more at US$0.055 per 10,000 operations compared to US$0.00036 for GPv1.
- For read operations, GPv2 costs US$0.004 per 10,000 operations, which is still higher than GPv1.
High transaction workloads might see increased costs with GPv2.
-
Determining Worth:
Depending on the ratio of storage to transaction costs for your workload:- Storage-Intensive Workloads: GPv2 provides cost savings for large-scale storage with fewer transactions.
- Transaction-Intensive Workloads: Evaluate whether the increased transaction costs offset storage savings.
Utilize Access Tiers for Blob Storage
To optimize storage costs, choose the appropriate access tier based on your data usage patterns.
-
Hot Tier:
- Best for frequently accessed data.
- Example: Application logs or frequently updated documents.
-
Cool Tier:
- Ideal for infrequently accessed data, offering ~44% savings compared to the Hot tier.
- Example: Backup data or data required for monthly reporting.
-
Cold Tier:
- Suited for rarely accessed data, with ~80% savings compared to the Hot tier.
- Example: Long-term data storage where data is accessed a few times a year.
-
Archive Tier:
- Designed for rarely accessed or regulatory data with ~89% savings compared to the Hot tier.
- Example: Archived transaction logs or regulatory compliance data.
Pricing Comparison Per GB/Month for LRS Storage (Australia East Region)
Access Tier | Price (USD per GB) | Cost Saving (%) |
---|---|---|
Hot | $0.0290 | N/A |
Cool | $0.0161 | 44% |
Cold | $0.0058 | 80% |
Archive | $0.00322 | 89% |
Consider Premium Blob Storage for High Transaction Workloads
Premium Blob Storage offers better performance and lower latency for high transaction workloads.
Premium blob storage provides access to block blobs and append blobs with low and consistent latency, with pricing optimized for high transaction rates.
Consider switching from Hot to Premium for:
- High-performance workloads.
- Scenarios where consistent low-latency access is critical.
Storage Cost Comparison (Australia East Region)
Tier | Cost per GB |
---|---|
Premium | $0.218 |
Hot | $0.020 |
- Hot Tier is significantly cheaper for larger storage volumes due to the lower cost per GB.
Transaction Cost Comparison (per 10,000 operations)
Tier | Writes | Reads | Iterative Reads |
---|---|---|---|
Premium | $0.033 | $0.0027 | $0.0330 |
Hot | $0.072 | $0.0060 | $0.0057 |
- Premium Tier has lower transaction costs, particularly for write-heavy workloads.
1. Hot Tier Use Case: Large Storage Volume
- Scenario: A company needs to store 50 TB of data with 10 million reads and 1 million writes per month.
- Cost Breakdown:
- Storage:
- Premium: ( 50 x 1,024 x 0.218 = $11,162 )
- Hot: ( 50 x 1,024 x 0.02 = $1,024 )
- Transactions:
- Premium: ( (1,000,000 x 0.033) + (10,000,000 x 0.0027) = $33 + $27 = $60 )
- Hot: ( (1,000,000 x 0.072) + (10,000,000 x 0.006) = $72 + $60 = $132 )
- Total Monthly Cost:
- Premium: ( 11,162 + 60 ) = $11,222
- Hot: ( 1,024 + 132 ) = $1,156
- Storage:
Hot tier is better for larger storage volumes with moderate transaction requirements.
2. Premium Tier Use Case: High Transaction Volume
- Scenario: A financial app writes 5 million records and reads 50 million records per month, with a storage requirement of 1 TB.
- Cost Breakdown:
- Storage:
- Premium: ( 1,024 x 0.218 = $223.23 )
- Hot: ( 1,024 x 0.02 = $20.48 )
- Transactions:
- Premium: ( (5,000,000 x 0.033) + (50,000,000 x 0.0027) = $165 + $135 = $300 )
- Hot: ( (5,000,000 x 0.072) + (50,000,000 x 0.006) = $360 + $300 = $660 )
- Total Monthly Cost:
- Premium: ( 223.23 + 300 ) = $523.23
- Hot: ( 20.48 + 660 ) = $680.48
- Storage:
Premium tier is better for high transaction volumes, especially write-heavy workloads.
Note: Prices vary based on Azure region. Review the Azure pricing calculator for up-to-date cost estimations.
Evaluate Locally Redundant Storage (LRS)
For workloads where geo-redundancy is not required, use LRS to save 50% compared to Geo-Redundant Storage (GRS). LRS provides adequate redundancy within a single Azure region for cost-conscious applications.
Automate Lifecycle Management
Set up Azure Storage lifecycle policies to:
- Move data automatically between access tiers.
- Delete data after its retention period has expired.
This minimizes manual effort and optimizes storage costs based on data usage trends.
Learn about lifecycle management
Use Reserved Capacity
Save up to 38% on storage costs by purchasing reserved capacity for predictable workloads with long-term commitments.
Performance Recommendations
Split Workloads Across Storage Accounts
For accounts using features like blobs, tables, or queues, consider splitting workloads.
- Use a Premium Storage account for blob-intensive operations.
- Retain Standard accounts for tables and queues.
This ensures workload-specific optimization.