Skip to content

Commit 5eff0e3

Browse files
committed
Update performance comparison
1 parent 0b8b974 commit 5eff0e3

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

README.md

+3-4
Original file line numberDiff line numberDiff line change
@@ -127,10 +127,9 @@ The ping API is also much nicer. gorilla/websocket requires registering a pong h
127127
which results in awkward control flow. With nhooyr/websocket you use the Ping method on the Conn
128128
that sends a ping and also waits for the pong.
129129

130-
In terms of performance, the differences depend on your application code. nhooyr/websocket
131-
reuses buffers efficiently out of the box if you use the wsjson and wspb subpackages whereas
132-
gorilla/websocket does not at all. As mentioned above, nhooyr/websocket also supports concurrent
133-
writers out of the box.
130+
In terms of performance, the differences mostly depend on your application code. nhooyr/websocket
131+
reuses message buffers out of the box if you use the wsjson and wspb subpackages.
132+
As mentioned above, nhooyr/websocket also supports concurrent writers.
134133

135134
The only performance con to nhooyr/websocket is that uses one extra goroutine to support
136135
cancellation with context.Context and the net/http client side body upgrade.

0 commit comments

Comments
 (0)