fix: increase memory to avoid unnecessary cpu spike related to GC

[mishraomp]

Increase heap size from 50 to 150MB to avoid unnecessary cpu spikes

Thanks for the PR!

Deployments, as required, will be available below:

• Frontend
• Backend

Please create PRs in draft mode. Mark as ready to enable:

• Analysis Workflow

After merge, new images are deployed in:

• Merge Workflow

---

Thanks for the PR!

Deployments, as required, will be available below:

• Frontend
• Backend

Please create PRs in draft mode. Mark as ready to enable:

• Analysis Workflow

After merge, new images are deployed in:

• Merge Workflow

[Copilot]

Pull request overview

This PR increases memory allocations to address CPU spikes caused by aggressive garbage collection. The changes adjust both the Kubernetes resource requests and the Node.js heap size limit to provide more headroom for the application.

• Node.js heap size increased from 50MB to 150MB (3x increase)
• Kubernetes memory requests increased from 75Mi to 200Mi (~2.67x increase) for both init and main containers
• Proper headroom maintained between heap size (150MB) and container memory (200Mi) for non-heap memory usage

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
charts/app/templates/backend/templates/deployment.yaml	Increases memory requests from 75Mi to 200Mi for both the init container (Flyway migrations) and main backend container
backend/Dockerfile	Increases Node.js max-old-space-size from 50MB to 150MB and updates the corresponding comment

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.