Graviton5 in Production at Honeycomb: Per-service Results From the m8g to m9g Migration

T1Covered by 1 source · first reported by Docker / HashiCorp / Grafana / Datadog / Honeycomb / Fly.io at 10 Jun, 13:00 UTC

This is the fourth installment in the Graviton retrospective series we've been writing since 2021. The methodology is the same one I always reach for: hold the workload constant, run both generations on the same Kubernetes namespace concurrently, and let the per-pod numbers speak.

clouddev

Sources

• T1Graviton5 in Production at Honeycomb: Per-service Results From the m8g to m9g MigrationDocker / HashiCorp / Grafana / Datadog / Honeycomb / Fly.io10 Jun, 13:00