too slow in multipart usage when use http/2 proto
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- rust
- Domain
- backend, networking
Research direction
No source file or test is named. Start with the multipart example and the bind_rustls_0_23 server setup, then reproduce the Chrome upload on Ubuntu with HTTP/1 and HTTP/2 to compare the slowdown. Done means the HTTP/2 multipart upload no longer shows the reported performance difference.
Written by the indexing model from the issue text.
Description
Your issue may already be reported! Please search on the Actix Web issue tracker before creating one.
Expected Behavior
post multipart data is fast when use http/2 proto
Current Behavior
upload file usage:
post multipart data is fast when use http/1 proto
but too slow when use http/2 proto
Possible Solution
Steps to Reproduce (for bugs)
- copy multipart example
- write a html form page to upload a file
- generate self signed certs, use bind_rustls_0_23 to run server
- use chrome to upload
Context
Your Environment
ubuntu 24.04 amd64
- Rust Version (I.e, output of
rustc -V): 1.82.0 - Actix Web Version: 4.9.0
- Dominant language
- Rust
- Stars
- 24.9k
- Forks
- 2k
- Avg merge
- 19h 9m
- Merged PRs (30d)
- 61
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from actix/actix-web
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
[actix-multipart] Generic "Payload error" when request exceeds size limitPossibly taken @robjtede claimed this 47 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
actix/actix-web#4168 · 4 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Change `HttpRequest::content_type` to return `Option<&str>`Possibly taken @Sruhvx-jpg claimed this 65 days ago. OpenA-http
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
actix/actix-web#3797 · 1 comment ·
Maintainers usually reply within 1 day
-
A-web C-improvement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
actix/actix-web#2666 · 4 comments · 2 reactions ·
Maintainers usually reply within 1 day
-
A-http A-web
Difficulty 4/5 3-5 days Newbie friendliness 20/100
Maintainers usually reply within 1 day
Similar issues
-
bug CLI exec session
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
compatibility
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aws/aws-emulator#30 · 1 comment ·
-
tormach-plasma refusal text with no machine reads "no machine is not declared a plasma machine"Openarea:post bug effort:low P2 source:agent
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Higher Interval Candles draws nothing on a seconds chart whose interval does not divide two hoursOpenbug studies
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
userFRM/egui-charts#2727 ·
Maintainers usually reply within 1 day