Skip to content

Reduce Java service memory limits#149

Merged
kenahrens merged 1 commit into
masterfrom
fix/java-memory-limits
Jun 10, 2026
Merged

Reduce Java service memory limits#149
kenahrens merged 1 commit into
masterfrom
fix/java-memory-limits

Conversation

@kenahrens

Copy link
Copy Markdown
Member

Summary

  • Heap 192→128MB, metaspace 160→128MB across all 3 Java services (api-gateway, accounts, transactions)
  • K8s memory limit 768→512Mi per pod, saving ~768Mi total across the 3 services
  • Dockerfile MaxRAMPercentage 75→50% as fallback default
  • Current usage is ~500Mi per pod at 2 req/s demo traffic — way overprovisioned

Test plan

  • Pods start without OOMKill on dev cluster
  • Memory usage stabilizes under 400Mi per pod
  • No increase in request errors or latency

🤖 Generated with Claude Code

Heap 192→128m, metaspace 160→128m, k8s limit 768→512Mi. These services handle 2 req/s demo traffic — the old settings reserved 1.3GB of Java heap across 3 pods for no reason.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@kenahrens kenahrens merged commit bf2969f into master Jun 10, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant