Cost saving with Standard SSD Billing Caps
As part of our commitment to continuously delivering increased value for our Azure Disk Storage customers, we are excited to introduce a cap on the number of billable Azure Standard SSD transactions. As a result, we have made changes to the billable transaction costs per hour that can result in additional cost savings.
The total cost of Azure Standard SSD Disk Storage depends on the size, number of disks, and the number of transactions. The number of transactions a disk can execute/perform/process is unchanged, so your disk will work as it always has been. However, the cost associated with these transactions is now limited and can help avoid greater costs.
The table below contains the maximum number of billable transactions for Standard SSD Disk Storage:
|
Product |
LRS Transaction Cap (# of Trx / hr) |
ZRS Transaction Cap (# of Trx / hr) |
|
E1 |
6,800 |
7,800 |
|
E2 |
13,400 |
15,400 |
|
E3 |
26,600 |
30,600 |
|
E4 |
43,400 |
61,000 |
|
E6 |
81,200 |
114,400 |
|
E10 |
147,200 |
214,000 |
|
E15 |
274,000 |
398,400 |
|
E20 |
502,000 |
737,600 |
|
E30 |
829,200 |
1,238,800 |
|
E40 |
893,000 |
1,344,700 |
|
E50 |
1,578,400 |
2,405,600 |
|
E60 |
2,777,500 |
4,243,900 |
|
E70 |
4,379,300 |
7,353,100 |
|
E80 |
9,478,400 |
14,706,200 |
If the number of hourly transactions listed on the table is reached, you will not incur additional transaction costs. The new pricing is effective March 6th, 2023 and applies to all the regions where Standard SSD is currently available.
Let’s review a few important details associated with this announcement.
Transactions on Azure Disks
On Azure, input/output operation per second (IOPS) and transactions are similar with one major exception:
A transaction on Azure is an I/O operation less than or equal to 256 KiBs of throughput. If your IO operation is larger than 256 KiBs of throughput, it is considered to require multiple transactions. The number of transactions is calculated by dividing the I/O size by 256 KiBs.
For example, an IO with the size of 1024 KiBs (1MiB) would be processed as 4 transactions on a Standard SSD disk.
Example of billed transaction caps
Let's look at an example to see how the new billing cap can help you save money. If you’re using an E4 disk with a block size of 4KiBs that averages 100 IOPS per month. With this block size 1 IO equals 1 transaction.
Previously without the transaction cap, the 100 transactions/second would have resulted in the following billable transactions:
Therefore, without this newly announced transaction cap, you would have been billed around $52 per month for an E4 SSD disk performing an average of 100 IOPS (transactions) for the transaction activity.
Now with the E4 disks having an hourly billable transaction cap of 43,400 transactions in an hour, your hourly bill with a Disk running at 100 IOPs would be:
Following the same example, let’s evaluate the cost of Standard HDD, which is cheaper per transaction than Standard SSD but does not have a cap on billable transactions:
360,000 billable transactions∗ $0.0005/10,000 Transactions∗ 730 hours/month=$13.31 per month
Your monthly Standard HDD transaction bill would add up to $13.31. That’s more than double the transaction bill would have been with cost you would incur by deploying a Standard SSD disk of the same capacity.
Standard SSD Benefits
In addition to the potential cost savings, upgrading from Standard HDD to Standard SSD has the following advantages:
- Increased service-level availability (SLA) of single-instance VM connectivity from 95 percent to 99.5 percent, improving availability guarantees.
- Reduced latency by 2X, making data retrieval faster while increasing application performance.
- Improved consistency of performance in terms of input/output operations and throughput, making your applications run more smoothly.
Published on:
Learn moreRelated posts
Update on classic storage account retirement and upcoming changes for classic storage customers
We previously announced that support would end for retired Azure classic storage accounts on 31 August 2024. Now that we are past the retireme...
Azure Elastic SAN for Azure VMware Solution: now Generally Available
Have you been looking to expand your storage on Azure VMware Solution (AVS), but do not need the extra compute performance and the associated ...
Accelerate metadata heavy workloads with Metadata Caching preview for Azure Premium Files SMB & REST
Azure Files previously announced the limited preview of Metadata caching highlighting improvements on the metadata latency (up to 55...
Announcing UNLIMITED Public Preview of Metadata Caching for Azure Premium SMB/REST File Shares
Azure Files is excited to announce the Unlimited public preview of Metadata Caching for the premium SMB/REST file share tier. Unlimited ...
Azure Backup-SAP HANA DB Backup Delivers More Value at Lower TCO with Reduced Protected Instance Fee
Azure Backup for SAP HANA Database Delivers More Value at Lower TCO with Reduced Protected Instance Fees starting 1st Sept’2024 At Azur...
Switch to Azure Business Continuity Center for your at scale BCDR management needs
In response to the evolving customer requirements and environments since COVID-19, including the shift towards hybrid work models and the incr...
The Azure Storage product group is heading to the SNIA Developer Conference 2024
The Azure Storage product group is heading to the SNIA Developer Conference (SDC) 2024 in Santa Clara, California, USA from September 16th thr...
Latest advancements in Premium SSD v2 and Ultra Azure Managed Disks
We are excited to share the latest advancements in Premium SSD v2 (Pv2) and Ultra disks, the next generation of Azure disk stor...
Unlocking the Potential of Unstructured Data with Microsoft Copilot and Azure Native Qumulo
It has been a true pleasure to see our friends at Qumulo constantly innovating and delivering a service that adds more value with every releas...
Public Preview: Customer Managed Planned Failover for Azure Storage
We are excited to announce customer managed Planned Failover for Azure Storage is now available in public preview. Over the past few ye...