-
Notifications
You must be signed in to change notification settings - Fork 364
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
change: [M#-8735] - Increase Cloud Manager node.js
memory allocation (development jobs)
#11084
Conversation
node.js
and TS
memory limits (development jobs)node.js
memory allocation (development jobs)
@@ -86,7 +86,7 @@ | |||
"zxcvbn": "^4.4.2" | |||
}, | |||
"scripts": { | |||
"start": "concurrently --raw \"vite\" \"tsc --watch --preserveWatchOutput\"", | |||
"start": "concurrently --raw \"NODE_OPTIONS='--max-old-space-size=4096' vite\" \"NODE_OPTIONS='--max-old-space-size=4096' tsc --watch --preserveWatchOutput\"", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From what I observed, it is only the tsc
process that has the OOM issue. I think we'd likely fix the issue by just apply the fix to the tsc
command, but at the same time, I don't think it will hurt having it on the Vite processes too
"start": "concurrently --raw \"NODE_OPTIONS='--max-old-space-size=4096' vite\" \"NODE_OPTIONS='--max-old-space-size=4096' tsc --watch --preserveWatchOutput\"", | |
"start": "concurrently --raw \"vite\" \"NODE_OPTIONS='--max-old-space-size=4096' tsc --watch --preserveWatchOutput\"", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be nice to update the "start" command to have -n vite,tsc
so we can better understand which process is crashing but we don't have to
For example:
"start": "concurrently -n vite,tsc \"vite\" \"tsc --watch --preserveWatchOutput\"",
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this could be done locally to debug the underlying issues in a separate task - we should have a separate ticket to investigate this - this PR facilitates development for now
Coverage Report: ✅ |
Cloud Manager E2E Run #6665
Run Properties:
|
Project |
Cloud Manager E2E
|
Run status |
Passed #6665
|
Run duration | 29m 10s |
Commit |
d37a032cb3: change: [M#-8735] - Increase Cloud Manager `node.js` memory allocation (developm...
|
Committer | Alban Bailly |
View all properties for this run ↗︎ |
Test results | |
---|---|
Failures |
0
|
Flaky |
8
|
Pending |
2
|
Skipped |
0
|
Passing |
435
|
Description 📝
Small PR to increase the memory allocation for Node.js for vite, TS compiler and storybook
Changes 🔄
How to test 🧪
Verification steps
yarn start
oryarn up
yarn storybook
As an Author I have considered 🤔
Check all that apply