title: Performance comparison of websocket implementations
body: <p><strong>EDIT:</strong> to prevent closing this question I'll just narrow it down to the essential.</p>
  
  <blockquote>
    <p>Can someone share a performance test in MB/s between the two websocket implementations listed below? Application or hardware details are irrelevant, just two crude numbers for a simple common scenario will suffice.</p>
  </blockquote>
  
  <hr>
  
  <p><strong>Original question</strong></p>
  
  <p>Did someone test the performance of these two websocket implemetations for <em>node.js</em>?</p>
  
  <ul>
  <li><a href="https://github.com/theturtle32/WebSocket-Node" rel="nofollow">WebSocket-Node</a></li>
  <li><a href="https://github.com/websockets/ws" rel="nofollow">ws</a></li>
  </ul>
  
  <p>I couldn't find anything recent (just a bunch of articles from 2012-2013). What I would like to see is:</p>
  
  <ul>
  <li>overhead (if at all, considering that actual <em>network</em> latency is more relevant I guess they both converge to 0)</li>
  <li>throughput (a simple MB/S figure for same application/hardware would be great)</li>
  <li>can <em>ws</em> really <strong>broadcast</strong> data on a network level (despite an underlying TCP? is this at all possible?) or is it just an abused method name (which actually sends the same message to many clients in a <code>for()</code> loop)?</li>
  </ul>
  
  <p>Even better:</p>
  
  <ul>
  <li>comparison of with/without Nagle's algorithm</li>
  <li>comparison of JSON vs binary messages</li>
  </ul>