-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
GC auto increase memory limit on inefficient GC #8687
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎
8 Skipped Deployments
|
✅ This change can build |
🟢 Turbopack Benchmark CI successful 🟢Thanks |
|
d0cd5a7
to
01eb47e
Compare
01eb47e
to
c847ae0
Compare
91c44f9
to
0967bee
Compare
c847ae0
to
d3d4e72
Compare
0967bee
to
0e94bb4
Compare
d3d4e72
to
1e800d3
Compare
arlyon
approved these changes
Jul 17, 2024
52a5ac9
to
cb65272
Compare
f7ec54f
to
ade4ad5
Compare
cb65272
to
20ed510
Compare
ade4ad5
to
3589b2e
Compare
20ed510
to
b4912c7
Compare
3589b2e
to
6fda947
Compare
b4912c7
to
d343e87
Compare
d343e87
to
e07d16a
Compare
GC until memory is reduced by 5% increase memory limit when needed
e07d16a
to
da4453b
Compare
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 25, 2024
### Description When GC is inefficient and can't collect enough memory, increase the provided memory limit automatically. We rather want to consume more memory than requested then crashing or hanging the compilation due to GC.
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 29, 2024
### Description When GC is inefficient and can't collect enough memory, increase the provided memory limit automatically. We rather want to consume more memory than requested then crashing or hanging the compilation due to GC.
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 29, 2024
### Description When GC is inefficient and can't collect enough memory, increase the provided memory limit automatically. We rather want to consume more memory than requested then crashing or hanging the compilation due to GC.
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Aug 1, 2024
### Description When GC is inefficient and can't collect enough memory, increase the provided memory limit automatically. We rather want to consume more memory than requested then crashing or hanging the compilation due to GC.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When GC is inefficient and can't collect enough memory, increase the provided memory limit automatically.
We rather want to consume more memory than requested then crashing or hanging the compilation due to GC.