Skip to content

fix: remove explicit Node heap cap from backend Dockerfile#411

Merged
plakkara-bc merged 1 commit into
devfrom
fix/remove-node-heap-cap
Jul 17, 2026
Merged

fix: remove explicit Node heap cap from backend Dockerfile#411
plakkara-bc merged 1 commit into
devfrom
fix/remove-node-heap-cap

Conversation

@mdiapenabc

Copy link
Copy Markdown
Collaborator

Removes the hardcoded --max-old-space-size=128 from the backend Dockerfile so Node.js uses its default heap sizing within the pod memory limit.

Let Node.js use its default heap sizing within the pod memory limit so we can validate behaviour on dev and test before prod.

@saifrazabc saifrazabc left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved to make Node.js max-old-space-size ( heap size ) as default, Let Node.js decide the heap.

@mdiapenabc
mdiapenabc marked this pull request as ready for review July 17, 2026 17:29
@plakkara-bc
plakkara-bc merged commit c6d66f6 into dev Jul 17, 2026
39 checks passed
@plakkara-bc
plakkara-bc deleted the fix/remove-node-heap-cap branch July 17, 2026 23:11
plakkara-bc added a commit that referenced this pull request Jul 17, 2026
fix: remove explicit Node heap cap from backend Dockerfile (#411)
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.

3 participants