-
Notifications
You must be signed in to change notification settings - Fork 11
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
parallel requests don't scale #14
Labels
Comments
stefan-guggisberg
added a commit
that referenced
this issue
Mar 17, 2020
trieloff
pushed a commit
that referenced
this issue
Mar 17, 2020
## [1.4.1](v1.4.0...v1.4.1) (2020-03-17) ### Performance Improvements * bumped fetch-h2 dependency and some housekeeping ([db66e1e](db66e1e)), closes [#14](#14)
fixed in db66e1e |
stefan-guggisberg
added a commit
that referenced
this issue
Apr 1, 2020
2 tasks
trieloff
pushed a commit
that referenced
this issue
Apr 2, 2020
# [1.6.0](v1.5.0...v1.6.0) (2020-04-02) ### Features * **index:** support array-type query param values ([fc07e7c](fc07e7c)), closes [#14](#14)
🎉 This issue has been resolved in version 1.6.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
The time to run parallel requests to the same http2 origin increases roughly linearly with the number of requests which is unexpected given HTTP/2 multiplexing.
Describe the solution you'd like
Either the underlying issue in
fetch-h2
gets fixed or we use an alternative implementation under the hood, e.g. node-fetch-h2.Describe alternatives you've considered
See above.
Additional context
grantila/fetch-h2#85
The text was updated successfully, but these errors were encountered: