Skip to content

Conversation

anonrig
Copy link
Member

@anonrig anonrig commented Jan 3, 2023

I couldn't verify this with the existing webstreams benchmarks. Opening in case somebody points me to the exact benchmark and/or provides one.

Referencing: oven-sh/bun#1708

@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/streams

@nodejs-github-bot nodejs-github-bot added the needs-ci PRs that need a full CI run. label Jan 3, 2023
@anonrig anonrig added performance Issues and PRs related to the performance of Node.js. web streams request-ci Add this label to start a Jenkins CI on a PR. labels Jan 3, 2023
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jan 3, 2023
@nodejs-github-bot
Copy link
Collaborator

@anonrig
Copy link
Member Author

anonrig commented Jan 3, 2023

@Jarred-Sumner
Copy link

Looks like this test fails https://github.com/nodejs/node/blob/master/test/parallel/test-stream-uint8array.js#L1-L102

Probably need to do something more specific than checking decoder

@RafaelGSS
Copy link
Member

The title says webstreams, but you are touching node.js streams. Could you please clarify?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-ci PRs that need a full CI run. performance Issues and PRs related to the performance of Node.js. web streams
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants