-
Notifications
You must be signed in to change notification settings - Fork 30k
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: writable buffering #28978
stream: writable buffering #28978
Conversation
Here they are: https://github.com/nodejs/node/blob/master/doc/guides/writing-and-running-benchmarks.md Be careful with this change, you are touching one of the worst hot paths in Node.js (together with |
The semversiness of this is a bit problematic, as this is likely to break some external users. |
@mcollina: this is definitly semver major. Is this something that you would even consider? If not please let me know so I don't spend time in vain :). |
dc5503a
to
a092cb8
Compare
I think it's worthwhile having a look if it could be simplified/improved the performance of it. |
a092cb8
to
23ee586
Compare
This should definitely be benchmarked to see if it's actually faster and how much. |
23ee586
to
b6a212f
Compare
b6a212f
to
3e51f4c
Compare
a2ce565
to
a8ba29c
Compare
Got the benchmark comparison working!
Seems like a negligible difference. Though the simplification part is still probably worth it. |
c0088f0
to
a5607bd
Compare
d99f8da
to
85b51a2
Compare
85b51a2
to
30cb4e6
Compare
@mcollina nothing I do here seems to make much of a difference... maybe not a hot path or maybe better benchmarks are needed? Or I'm doing something wrong... The current benchmark mostly test sync writing... which I don't think is a good real-world example. |
bfc1416
to
cd6006c
Compare
Note this also changes the behaviour so that |
53164df
to
df77306
Compare
df77306
to
69a6436
Compare
69a6436
to
9033d42
Compare
this is WIP |
Simplify and optimize writable stream buffering.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes