3 months ago
Pinned Solution
3 months ago
go to your service settings → deploy → resource limits and bump up the ram slider to like 16-32gb. also add this in your service variables tab
NODE_OPTIONS=--max-old-space-size=16384also check and remove any hardcoded --max-old-space-size from Dockerfile ENV statements or package.json start scripts or any launch commands node.js should auto-detect container limits if not hardcoded.
4 Replies
3 months ago
go to your service settings → deploy → resource limits and bump up the ram slider to like 16-32gb. also add this in your service variables tab
NODE_OPTIONS=--max-old-space-size=16384also check and remove any hardcoded --max-old-space-size from Dockerfile ENV statements or package.json start scripts or any launch commands node.js should auto-detect container limits if not hardcoded.
3 months ago
because resource limits control the maximum amount of resources available to a service
3 months ago
let me know if this resolve your issue
3 months ago
perfect
Status changed to Solved brody • 3 months ago