t3vsm6id
Size for size, t3 is on average 35% cheaper than m6id on demand in US East (N. Virginia), across 3 shared sizes. A burstable type against a general-purpose one with the same vCPUs and memory.
On-demand prices by size in US East (N. Virginia)
USD per hour for PostgreSQL, Single-AZ. Pick a size to compare the two types.
| Size | t3 | m6id | m6id vs t3 |
|---|---|---|---|
| large | db.t3.large $0.145 | db.m6id.large $0.224 | ▲ 54% |
| xlarge | db.t3.xlarge $0.29 | db.m6id.xlarge $0.448 | ▲ 54% |
| 2xlarge | db.t3.2xlarge $0.579 | db.m6id.2xlarge $0.897 | ▲ 55% |
Key differences
The biggest lead each family has.
Where t3 leads
On-demand priceCheaper in 3 of 3 shared sizes
35% cheaperWhere m6id leads
Sizes10 sizes here vs 6
4 moreLargest size128 vCPUs vs 8
BiggerKeep exploring
Each family's own page, and how it compares with others.