Migration to Graviton 5: What upgrading our ClickHouse cluster actually accomplished
Blog post from Dash0
A production ClickHouse cluster was upgraded from AWS Graviton 4 m8g.48xlarge instances to same-sized Graviton 5 m9g.48xlarge instances, retaining identical CPU count, memory, storage, software, data structures, and Keeper configuration to isolate hardware effects. Although the new instances cost 9% more per hour, a before-and-after analysis of comparable weekday workloads, standardized by query type and baseline traffic mix, found that they used about 23% less cluster CPU and reduced CPU consumption per byte by 21% for reads, 28% for writes, and 33% for asynchronous insert flushing. Overall SELECT latency improved substantially despite a 17% increase in query volume, with median latency falling 48% and p95, p99, and p99.9 latency improving by roughly 59–63%; background merge throughput also rose 41%, while slow merges became 29% faster. The higher hourly price therefore translated to lower effective cost per unit of work, estimated at 13.9% cheaper for reads, 21.3% cheaper for inserts, and 15.8% cheaper on average cluster CPU usage. Broader adoption is currently constrained by regional availability of Graviton 5 instances and the absence of memory-optimized r9g types.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.