d******e
发帖数: 2265 | 1 https://github.com/ericmoritz/wsdemo/blob/results-v1/results.md
Summary
Implementation Connection Time (mean) Latency (mean) Messages
Connections Connection Timeouts
Erlang 865ms 17ms 2849294 10000 0
Haskell (Snap) 168ms 227ms 1187413 4996 108
Java (Webbit) 567ms 835ms 1028390 4637 157
Go 284ms 18503ms 2398180 9775 225
Node.js (websocket) 768ms 42580ms 1170847 5701 4299
Python (ws4py) 1561ms 34889ms 1052996 4792 5208
貌似node不行阿 |
i**i
发帖数: 1500 | |
d******e
发帖数: 2265 | 3 go也很猛
意外的是 Haskell 居然更强
算是排名第三
【在 i**i 的大作中提到】
: for node.js, just follow socket.io.
: https://medium.com/node-js-javascript/finding-the-right-node-js-websocket-
: implementation-b63bfca0539
|
N******K
发帖数: 10202 | 4 latency 为啥会差这么多？
【在 d******e 的大作中提到】
: https://github.com/ericmoritz/wsdemo/blob/results-v1/results.md
: Summary
: Implementation Connection Time (mean) Latency (mean) Messages
: Connections Connection Timeouts
: Erlang 865ms 17ms 2849294 10000 0
: Haskell (Snap) 168ms 227ms 1187413 4996 108
: Java (Webbit) 567ms 835ms 1028390 4637 157
: Go 284ms 18503ms 2398180 9775 225
: Node.js (websocket) 768ms 42580ms 1170847 5701 4299
: Python (ws4py) 1561ms 34889ms 1052996 4792 5208
|
i**i
发帖数: 1500 | 5 用socket.io, 只要估计最大同时连接的用户数目，堆机器就应该可以了。 单个机器可
以支持几千个同时连接。
【在 i**i 的大作中提到】
: for node.js, just follow socket.io.
: https://medium.com/node-js-javascript/finding-the-right-node-js-websocket-
: implementation-b63bfca0539
|
i**i
发帖数: 1500 | 6 没仔细看。这个测试好像不靠谱。
负载太大，不太合理。有点系统崩溃的意思。
确定都是单线程？
【在 N******K 的大作中提到】
: latency 为啥会差这么多？
|
m********5
发帖数: 17667 | 7 我看到就想: what the crap!?
结果一看原始连接，发现果然是crap, 这个link是个过期的git tag，2012年的！
再看原作者当时怎么说：
http://www.reddit.com/r/programming/comments/v5ap8/web_server_b
I wrote the thing and I can tell you that yes, these results are pretty much
crap. I incorrectly used Folsom, the project I used to collect the stats.
Folsom is meant for realtime monitoring and not what I used it for. It only
keeps 60 second windows of the data it produces. That means all times prior
to the fine 60 second window was thrown out.
I tweeted the results at 3am to get feedback from folks I know.
Unfortunately it spread across the net really fast.
虽然最后他自已又更正了说法，但是可见原作者在做这个benchmark的时候是个新手，
很多细节可能是错误的，他的这个结果，我看没有参考意义。
I'm sorry I was mistaken that Folsom only keeps a 60 second window. It has
support for sliding windows but its default is to use the entire dataset for
histograms and percentiles. I take back my statement that the result were
pretty much crap. They're only slightly crappy because I used a m1.medium
box.
I'm spending my free time this week to make the benchmark more automated so
that it is easier for someone who volunteered to run it in their datacenter
on real hardware. That should produce a much fairer result.
【在 d******e 的大作中提到】
: https://github.com/ericmoritz/wsdemo/blob/results-v1/results.md
: Summary
: Implementation Connection Time (mean) Latency (mean) Messages
: Connections Connection Timeouts
: Erlang 865ms 17ms 2849294 10000 0
: Haskell (Snap) 168ms 227ms 1187413 4996 108
: Java (Webbit) 567ms 835ms 1028390 4637 157
: Go 284ms 18503ms 2398180 9775 225
: Node.js (websocket) 768ms 42580ms 1170847 5701 4299
: Python (ws4py) 1561ms 34889ms 1052996 4792 5208
|
