The instance type used has 8 vCPUs and are selected to support a larger number of database threads in a production workload.
| Instance Type | Resource Specs | Price Per Hour (us-east) |
|---|---|---|
| db.m5.2xlarge | 8 vCPUs, 32GB RAM | $0.68 (MySQL) ($0.71 PostgreSQL) |
| db.r6g.2xlarge | 8 vCPUs, 64GB RAM | $0.86 (MySQL) ($0.90 PostgresSQL) |
| db.r7g.2xlarge | 8 vCPUs, 64GB RAM | $0.96 (MySQL & PostgreSQL) |
Last week I had the opportunity to speak at the MySQL and Heatwave Summit in San Francisco. I discussed the impact of the new MySQL 8.0 default caching_sha2_password authentication, replacing the mysql_native_password authentication that was the default for approximately 20 of the 30 years that MySQL has existed.
Read moreAt the MySQL and Heatwave Summit 2025 today, Readyset announced a new data systems architecture pattern named Readyset QueryPilot . This architecture which can front a MySQL or PostgreSQL database infrastructure, combines the enterprise-grade ProxySQL and Readyset caching with intelligent query monitoring and routing to help support applications scale and produce more predictable results with varied workloads.
Read moreIn a CPU-bound database workload, regardless of price, would you scale-up or scale-new? What if price was the driving factor, would you scale-up or scale-new? I am using as a baseline the first available AWS Graviton2 processor for RDS (r6g).
Read more
