title: SSL session tickets vs session ids
body: <p>To improve SSL handshake performance for not retaining(short) connections there are two separate features known widely:</p>
  
  <ul>
  <li>TLS session ids</li>
  <li>TLS session tickets</li>
  </ul>
  
  <p>In case of very many short connection sessions which mechanism in terms of performance overhead is preferable and should be used?</p>
  
  <p>I know server need to cache session ids, also session tickets are easily shareable in case of load balancing, but let's assume there is a single server listening on a single port(no load balancing) and it receives very many SHORT incoming TLS connection sessions.</p>
  
  <p>So which approach (sessions or tickets) is preferable given this scenario?</p>