Skip to content
Dev.to1 min read

How We Cut Rails on GKE Costs by 60%: The...

tl;dr: We reduced Google Kubernetes Engine(GKE) costs by 60%. The biggest wins came not from Kubernetes tuning, but from understanding why our Rails app needed so many Pods in the first place: Rails was running 1 Puma worker with 33 threads. Ruby's GVL made this effectively single-core. We switched to 4 workers with 8 threads. API authentication used bcrypt on every request. We replaced it with a lighter method. GKE node generation was outdated: upgrading from n1 to n2d gave 56% more CPU, 23% mo
Read original on dev.to
0
0

Comment

Sign in to join the discussion.

Loading comments…

Related

Get the 10 best reads every Sunday

Curated by AI, voted by readers. Free forever.

Liked this? Start your own feed.

0
0