@tatsuhiro-t we now see in our testing of 50 parallel downloads of 100MB (with an apache backend) that nghttpx runs at 100% cpu and curl at about 67% on a debian sid.

The download speed then depends on the machine. My old one goes to ~500MB/s and @bagder's beast goes to ~1000 MB/s. The cpu ratios stay.

Just an FYI what we are currently seeing with your nice work. Thanks!

Clarification: that is on localhost, but the MTU stays at 14xx bytes. I imagine that a third of the nghtpx cpu goes into the backend fetch.

Your curl work does the brilliant job here, great work.
Yeah, basically a proxy does 2 things that are client and server, roughly doing 2x work and CPU usage tends to be higher. I made some optimization in the current nghttp2 master, so hopefully the next nghttp2 release will improve the situation a little bit. Building nghttpx including ngtcp2, and nghttp3 with LTO enabled also boosts a little bit of RPS (~10%).