SSL session caching and reuse

For improved performance, EAServer caches SSL session identifiers and allows clients to reuse them. Since creating an SSL session requires CPU-intensive computations, SSL session reuse results in a relatively large performance gain over setting up completely new security sessions for each connection. The settings on the Advanced tab control how SSL clients can reuse sessions for subsequent and simultaneous connections.

Cached sessions allow the client to reuse a session in a subsequent connection. The SSL Cache Size setting controls how many entries can be cached. Set this to a number less than or equal to the maximum connections setting for the server. The cache requires approximately 64 bytes per entry. The SSL Session Linger value specifies how long cached session IDs remain valid.

The SSL Session Share setting specifies how many simultaneous connections can share one session ID. Session sharing can improve performance when the client opens multiple connections simultaneously. For example, a browser client may open several connections at once to download images linked to an HTML page. Session sharing allows the client to reuse the session for the second and subsequent connections, up to the number of concurrent connections specified by the SSL Session Share value.

NoteThese are advanced SSL parameters. They should be set only by someone who is knowledgeable about SSL.