feat: add max node size to prevent OOM #76
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
|
|
Duslia
force-pushed
the
feat/max_node_size
branch
from
1a9a6df
to
68516bd
Compare
Hchenn
changed the title
Duslia
force-pushed
the
feat/max_node_size
branch
6 times, most recently
from
c64b10f
to
89da2a1
Compare
Duslia
force-pushed
the
feat/max_node_size
branch
3 times, most recently
from
4642202
to
db63ef9
Compare
Duslia
force-pushed
the
feat/max_node_size
branch
from
db63ef9
to
750c63d
Compare
Hchenn
changed the title
joway
approved these changes
Jan 11, 2022
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.
If there are only few big requests, add MaxNodeSize to avoid allocating a large memory for each request.
Don't change this value unless you know what you are doing.