Halodoc migrated their Amazon EKS workloads from Graviton3 to Graviton4 processors, achieving 35% cost savings through a data-driven approach. The migration involved two-phase validation: hardware benchmarking with Sysbench showed 28% CPU throughput improvement and 64% memory bandwidth gains, while application-level testing with JMeter demonstrated lower latency and resource utilization. By combining the processor upgrade with strategic resource right-sizing (15% CPU and 10% memory reduction), they reduced node count by 40% and maintained performance while cutting costs. The zero-downtime migration used controlled node pool rebalancing, followed by a one-week stabilization period before applying resource optimizations.

9m read timeFrom blogs.halodoc.io
Post cover image
Table of contents
Why Look Beyond Graviton3?Our Evaluation ApproachPhase 1: Hardware Benchmarking using SysbenchPhase 2: Application-Level Benchmarking using JMeterThe Bigger Win: Resource Right-SizingStrategic Adoption & Cost AnalysisHow We Rolled Out Graviton4 in EKS (Zero-Downtime Migration)NodePool UpdatesControlled RebalancingPost-Migration Validation and Resource OptimizationCost ImpactClosing ThoughtsJoin usAbout HalodocTags

Sort: