Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Have more honest performance comparison in README.md #82

Merged
merged 1 commit into from
May 30, 2019
Merged

Have more honest performance comparison in README.md #82

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,8 +125,8 @@ it has to reinvent hooks for TLS and proxies and prevents support of HTTP/2.
Some more advantages of nhooyr/websocket are that it supports concurrent writes and makes it
very easy to close the connection with a status code and reason.

In terms of performance, there is no significant difference between the two. Will update
with benchmarks soon ([#75](https://github.com/nhooyr/websocket/issues/75)).
In terms of performance, the only difference is nhooyr/websocket is forced to use one extra
goroutine to provide native context support. Otherwise, they should perform identically.

### x/net/websocket

Expand Down