In the past week I’ve added some more reading to my list, extended the library and hammered the credit card. Some of this has been in part to keep abreast of things as a result of being quizzed in job interviews.
At 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.
In 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).
As part of using public datasets with my own Benchmarking Suite I wanted upsize a dataset for larger volume testing.
I have always used the INFORMATION_SCHEMA.TABLES data_length and index_length columns as a sufficiently accurate measurement for actual disk space used.