AWS Graviton: Discover the Power of Distributed SQL + Graviton
summary
Benchmarks compare YugabyteDB on AWS Graviton2 c6g vs c5 instances using sysbench; initial CentOS 8 builds hit excessive disk bandwidth because of a 64k page size causing throttling at ~6k IOPS, so tests move to Ubuntu/Amazon Linux 2. Enabling link time optimization (LTO) on ARM builds closes the read-performance gap with Intel, but write throughput remains lower. Plan is to migrate free-tier instances to t4g and continue tuning for Graviton3 trials.
AI-written summary · about
chapters (12)
- 0:00AWS Graviton and YugabyteDB intro
- 1:25AWS Graviton processors overview
- 3:58Graviton 2 architecture
- 7:35Graviton 2 instances and pricing
- 10:44Graviton 2 price performance
- 11:48Graviton 3 processors intro
- 14:20YugabyteDB on Graviton performance
- 16:25YugabyteDB benchmarks: Intel vs Graviton
- 19:56Debugging CentOS performance
- 21:04Optimizing YugabyteDB for Graviton
- 22:49YugabyteDB Cloud on Graviton testing
- 24:12Next steps for YugabyteDB and Graviton
related talks
22mGraviton
19mMaximize database price performance with Aurora and Graviton2 instances
20mAWS On Air ft. AWS Graviton3 Processors and Amazon EC2 C7g Instances
25mAdopt AWS Graviton2 instances for best price-performance in EC2
45mAWS Graviton: Best Price Performance for your AWS Workloads
49mBuilding real-time applications to utilize AWS Graviton
20mRunning mission-critical applications on AWS sustainably
01h 01mEstimate your Graviton ROI for improved price performance & sustainability
