Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Assuming you don't count connection set-up (as you indicated in your update), it strongly depends on the cipher chosen. Network overhead (in terms of bandwidth) will be negligible. CPU overhead will be dominated by cryptography. On my mobile Core i5, I can encrypt around 250 MB per second with RC4 on a single core. <strike>(RC4 is what you should choose for maximum performance.)</strike> AES is slower, providing "only" around 50 MB/s. So, if you choose correct ciphers, you won't manage to keep a single current core busy with the crypto overhead even if you have a fully utilized 1 Gbit line. [<strong>Edit</strong>: RC4 should not be used because it is no longer secure. However, AES hardware support is now present in many CPUs, which makes AES encryption really fast on such platforms.]</p> <p>Connection establishment, however, is different. Depending on the implementation (e.g. support for TLS false start), it will add round-trips, which can cause noticable delays. Additionally, expensive crypto takes place on the first connection establishment (above-mentioned CPU could only accept 14 connections per core per second if you foolishly used 4096-bit keys and 100 if you use 2048-bit keys). On subsequent connections, previous sessions are often reused, avoiding the expensive crypto.</p> <p>So, to summarize:</p> <p><strong>Transfer on established connection:</strong></p> <ul> <li>Delay: nearly none</li> <li>CPU: negligible</li> <li>Bandwidth: negligible</li> </ul> <p><strong>First connection establishment:</strong></p> <ul> <li>Delay: additional round-trips</li> <li>Bandwidth: several kilobytes (certificates)</li> <li>CPU on client: medium</li> <li>CPU on server: high</li> </ul> <p><strong>Subsequent connection establishments:</strong></p> <ul> <li>Delay: additional round-trip (not sure if one or multiple, may be implementation-dependant)</li> <li>Bandwidth: negligible</li> <li>CPU: nearly none</li> </ul>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload