-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
stream: add global Stream.defaultHighwaterMark #40511
Conversation
@nodejs/streams @nodejs/buffer |
Some background for this. In high memory environment we usually override |
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.
Ideally this would also have a test that sets Buffer.poolSize and checks hwm
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 should be its own commit or possibly its own PR.
I agree with the change.
What should be? |
Split into 2 commits |
cc @nodejs/tsc - wdyt the severity of this should be? Should we backport this change to LTS lines? |
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.
lgtm
Doesn't it need a test? |
… semver-major? It’s a pretty big potential increase in memory usage for people who increase the buffer pool size but not the stream HWMs. |
Either major or minor with do-not-backport labels, i.e. I don't think this should land in a LTS line. I'm slightly for the minor with do-not-backports but I'm good either way. I don't expect a significant increase in memory usage but I expect an improvement in throughput. |
IMO semver-minor |
needs tests |
Co-authored-by: Vitaly Kuzmich <[email protected]>
Co-authored-by: Mestery <[email protected]>
Co-authored-by: mscdex <[email protected]>
Missing documentation for |
No description provided.