What version of Go are you using (go version)?
$ go version
go version go1.17.6 darwin/amd64
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/anton/Library/Caches/go-build"
GOENV="/Users/anton/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/anton/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/anton/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.17.6"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/3_/brw14zgj1sd1x1hnnz4p02tm0000gn/T/go-build266993821=/tmp/go-build -gno-record-gcc-switches -fno-common"
What did you do?
I'm running a websocket client application consuming lots of short messages from its established websocket connection.
What did you expect to see?
I would like to have no allocations for Conn.Read calls.
What did you see instead?
Each call of Conn.Read allocates one atLeastReader while going through Conn.readFromUntil.
There also were some redundant allocations fixed in #50657.
Combining #50657 with the patch I'm currently doing makes Conn.Read have zero allocations.
What version of Go are you using (
go version)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env)?go envOutputWhat did you do?
I'm running a websocket client application consuming lots of short messages from its established websocket connection.
What did you expect to see?
I would like to have no allocations for
Conn.Readcalls.What did you see instead?
Each call of
Conn.Readallocates oneatLeastReaderwhile going throughConn.readFromUntil.There also were some redundant allocations fixed in #50657.
Combining #50657 with the patch I'm currently doing makes
Conn.Readhave zero allocations.