This blog walks through Migrating Production Workloads from Graviton3 to Graviton4

HaloDoc is a healthcare technology platform that offers telemedicine services, online pharmacy, and health information resources to users in Indonesia. Through its platform, HaloDoc aims to improve access to healthcare services, empower patients to take control of their health, and facilitate collaboration between healthcare providers. Developers can learn from HaloDoc's innovative use of technology to address healthcare challenges, leveraging telemedicine, artificial intelligence, and data analytics to enhance patient care and outcomes.

Halodoc

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.

Reducing Amazon EKS Compute Costs by 35%: Migrating Production Workloads from Graviton3 to Graviton4

Phase 1: Hardware Benchmarking using Sysbench

Phase 2: Application-Level Benchmarking using JMeter

How We Rolled Out Graviton4 in EKS (Zero-Downtime Migration)

Post-Migration Validation and Resource Optimization