David Fifield 3df514ae29 Call WriteMessage directly in websocketconn.Conn.Write. ... In the client←server direction, this hits a fast path that avoids allocating a messageWriter. https://github.com/gorilla/websocket/blob/v1.5.0/conn.go#L760 Cuts the number of allocations in half in the client←server direction: $ go test -bench=BenchmarkReadWrite -benchmem -benchtime=5s BenchmarkReadWrite/c←s_150-4 597511 13358 ns/op 11.23 MB/s 33709 B/op 2 allocs/op BenchmarkReadWrite/s←c_150-4 474176 13756 ns/op 10.90 MB/s 34968 B/op 4 allocs/op BenchmarkReadWrite/c←s_3000-4 156488 36290 ns/op 82.67 MB/s 68673 B/op 5 allocs/op BenchmarkReadWrite/s←c_3000-4 190897 34719 ns/op 86.41 MB/s 69730 B/op 8 allocs/op		2022-11-16 13:48:34 -07:00
..
websocketconn.go	Call WriteMessage directly in websocketconn.Conn.Write.	2022-11-16 13:48:34 -07:00
websocketconn_test.go	Benchmark for websocketconn.Conn read/write.	2022-11-16 13:48:34 -07:00