GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||||||||
GeezerVison is showing github.com — stream: improve `Readable#from` perf by rluvaton · Pull Request #50359 · nodejs/node Conversation
|
|
Review requested:
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Not sure I'm convinced the extra complexity is worth it. Let's see what the benchmark says. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@rluvaton when you start a benchmark ci in cases like this, add a filter e,g, |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/1457/ |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
I'm -0. There is a perf improvement but the maintainability cost is quite high. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
due to the removal of the async modifier I rerun the benchmark:
I'm on the fence as well... |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@ronag Updated the benchmarks... |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I'm tired so if I don't make sense let me know - In the array case can't we just set the stream's buffer to |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
bdcda68 to
aa3d6c2
Compare
it would really improve the performance for sure but wouldn't it be dangerous as we need to make the stream reach the state where it would have data after init and everything |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Not really? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Yeah that was my point in #50359 I think that would be way faster and probably semver-major |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Because it needs a semver major, I will create a new PR with the new code after that |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
e5352d6 to
ae6dd74
Compare
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Landed in 10d51e8 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
PR-URL: #50359 Reviewed-By: Vinícius Lourenço Claro Cardoso <[email protected]> Reviewed-By: Robert Nagy <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]>
PR-URL: #50359 Reviewed-By: Vinícius Lourenço Claro Cardoso <[email protected]> Reviewed-By: Robert Nagy <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]>
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.