title: Jetty WebSocket performance
body: <p>On the Jetty page <a href="https://webtide.com/why-choose-jetty/" rel="nofollow">https://webtide.com/why-choose-jetty/</a> in the <em>Throughput</em> section it says: </p>
  
  <blockquote>
    <p>We have designed Jetty for scalable performance under realistic loads of many simultaneous connections and we can achieve excellent results with many tens of thousands of HTTP connections and hundreds of thousands of simultaneous WebSocket connections.</p>
  </blockquote>
  
  <p>So, what it is so different in the implementation of these 2 protocols, how Jetty can handle only tens of thousands of HTTP connections and in magnitude more WebSocket connections? Are WebSocket connections less expensive? How it can be? If both HTTP and WebSocket implementations utilize Java NIO (just guessing), why there is a difference in the performance then?</p>