-
Notifications
You must be signed in to change notification settings - Fork 7
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
fetch #11
Comments
I believe we should be much more descriptive about what we want to talk about, and add a Github issue template. My ideal performance issue would be:
|
This is mostly referring to the WHATWG streams or there is something more underneath? |
I don't think this is done. I haven't seen any evidence of it, I still see a significant gap compared to http.request. |
Here is the latest data I have collected on Node.js v19.14.0:
We could say that the major blocker are WHATWG streams, but I would not consider this "done". We still need a 2x throughput increase |
@mcollina today's release will include a perf improvement on webstream errors. It should improve a bit. |
There is a massive improvement in main:
We still need a rough +50% increase. |
We can do it! I think I'll have time next week to work on this. |
@mcollina, this is the rough +100% increase you were looking for (I guess). |
That actually should not just improve |
I'm not really quite sure. The amount of |
What about the WHATWG, has been any further research for them? |
This keep being closed, but either all the fixes needed are not released yet or there is some other problem:
As you can see there is a staggering gap between what is possible (undici This issue should not be closed until fetch reaches the same level of |
Refs: nodejs/undici#1203
Refs: #9
The text was updated successfully, but these errors were encountered: