-
Notifications
You must be signed in to change notification settings - Fork 76
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.
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
Other options for Go #9
Comments
Did a brief (read: ugly) conversion w/ gorilla -- noticeably faster. May have a chance to add a gorilla version this week. |
Added a gorilla server in the same style as the current. Would be interesting to compare with a channel based impl like the gorilla chat example: https://github.com/gorilla/websocket/tree/master/examples/chat Pull #23 |
I merged the gorilla implementation. |
Finally got a chance to run all the benchmarks with all the new implementations. The new test is a little more demanding so absolute numbers are lower. Current leader is Node with uws at 26k (though that was a single run that I was unable to reproduce...) Best reproducible is Haskell at 25k. Gorilla came in at 20k. Normal Go websocket package came in at 22k. Not what I was expecting, but I ran the tests multiple times and these numbers seemed fairly consistent. See results/result-02.md for the raw data. |
Thanks for writing up the article. As a user of both Go and Elixir, it's in line with what I'd expect.
There are a few other options for Go though, which I wonder how they compare in terms of ease-of-use and performance.
https://github.com/jingweno/thunderbird
https://github.com/gorilla/websocket
Not sure if I'll have a chance to send a PR anytime soon, but if anyone else would like to, that'd be awesome.
The text was updated successfully, but these errors were encountered: