node.js - Performance comparison of websocket implementations -


edit: prevent closing question i'll narrow down essential.

can share performance test in mb/s between 2 websocket implementations listed below? application or hardware details irrelevant, 2 crude numbers simple common scenario suffice.


original question

did test performance of these 2 websocket implemetations node.js?

i couldn't find recent (just bunch of articles 2012-2013). see is:

  • overhead (if @ all, considering actual network latency more relevant guess both converge 0)
  • throughput (a simple mb/s figure same application/hardware great)
  • can ws broadcast data on network level (despite underlying tcp? @ possible?) or abused method name (which sends same message many clients in for() loop)?

even better:

  • comparison of with/without nagle's algorithm
  • comparison of json vs binary messages

edit: updated info newer, faster implementation

i integrate here nick newman's jun 17 '16 @ 20:08 comment avoid getting lost means.

a newer , faster implementation of websockets uws. promising results reported several devs. simple cases it's no-brainer. below discussion therefore superseded.


i wonder why nobody answer question. so, after more hours of search i've done before came page answers given.

i post here , answer own question others searching find easier.

the page benchmark comparison of ws. yes, it's pretty straightforward it's somehow buried away.

here relevant results:

in case want send 4-16kb json messages (even 4kb exaggeration, messages 100-200 characters). first graph shows 64kb there's no appreciable difference @ all. larger messages (around 16mb) becomes increasingly evident ws faster websocket-node.

for binary messages, both same (if not identical). makes me wonder if somehow borrowed code each other on github. nice btw both are on github shared , forked , on.

the following graphs show message fragmentation, relevant streaming, i'm not interested in. above answers question:

  1. performance identical non-fragmented text messages (up 16mb)
  2. performance identical non-fragmented binary messages (no size limit)

Comments

Popular posts from this blog

Fail to load namespace Spring Security http://www.springframework.org/security/tags -

sql - MySQL query optimization using coalesce -

unity3d - Unity local avoidance in user created world -