c# - How can I optimize SSL session so I can reuse it later (if needed) to improve Client Server performance -

I have a server running Windows Azure (the link is in the SSL certificate to show the big key),

On this basis, a large key will be more expensive to setup and will come down from the CPU perspective.

Let's say I'm one. I am using .NET client and .NET server; What changes should I make to reduce the overhead of connecting / disconnecting an SSL perspective (if any).

For the purpose of this conversation, include these scenarios (if you can think of them, add more)

• IIS from web browsers < WCF client WCF client (IIS)
• WCF client for WCF TCP
• Socket-based client socket-based server

  The cost of the initial handshake is basically fixed (fixed parameters are given). Resume handshake costs almost nil.

  The way to improve performance is to increase the amount of sessions that resume sessions, and not the initial session. This reduces the cost of initial handshake in the resumed handshake, the average handshake reduces the cost.

  The easiest way to increase the handshake rate started again is to have a big session cache size / timeout. Of course, having a large session cache can cause self-display problems. There is a need to find a good balance between the two, and the best way to do this is with the test.