x/net/http2: request-response loop is ~2-3 times slower on http2 than on https #18309
Comments
bradfitz
changed the title
|
I don't think anyone will have a chance to look at this in detail until after Go 1.8 is released. In the meantime, the following may help:
Brad has done some optimization work for grpc-over-http2 that may help. I'm not sure if all of those optimizations have been submitted yet.
I wouldn't expect a speedup. The https version probably pipelines all 100k requests over just 10 TCP connections. I doubt you will see any benefits from muxing all requests onto a single TCP connection unless you're on a congested WAN or have many fewer requests-per-connection. That said, a 2x slowdown is not expected. Thanks for the report. |
|
Hi and thanks for your response. I've tested with current master Here are profiles made with go 1.7.4: (http2, one client per goroutine) I understand that 10 keepalive https connections might be faster than one http2 connection but don't understand why are they faster than 10 http2 connections. Also I've tested this very client against nginx http2 server with the same response size and for some reason using one http2 connection in client is faster than 1 per goroutine. Have no idea why |
|
@Scratch-net, can you try with Go 1.9? There are a few HTTP/2 performance improvements for the 1.9 release. |
tombergan
added
the
WaitingForInfo
|
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
What version of Go are you using (
go version)?go version go1.7.4 linux/amd64
What operating system and processor architecture are you using (
go env)?GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/root/go"
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build416699138=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
What did you do?
I need a fastest way to securely communicate between microservices. And I tested request-responce loop with https and http2. Client starts 10 goroutines and each of them does 10k requests to server
And it turned out that https is 2 to 3 times faster when sending and receiving relatively small amounts of data(129 bytes request, 173 bytes response)
Server: https://play.golang.org/p/22hOHrHNZs
Client: https://play.golang.org/p/OdEh9cUvah (change IP on line 42)
I have 2 2xcpu servers with ~1 ms latency between them
When I run this test with http2 enabled it takes about 14 seconds for 100k requests divided in 10 goroutines
without http2 it takes about 7 seconds
Moreover, if I reuse client between goroutines it takes ~24 seconds on http2.
What did you expect to see?
A speed up between client and server when using http2
What did you see instead?
2x slowdown
The text was updated successfully, but these errors were encountered: