Open topic with navigation

Server Options for HTTP Multiplexing

Once a server sends a complete response to a client request, instead of closing the server connection, FortiADC keeps the connection open and places a record for the connection into a pool of connections available for re-use. The connection will be re-used by FortiADC when another client request is load balanced to the same server.

The reusable connection pool record for a server connection is only removed when either the server closes the connection, or the Reused Connection Timeout expires (see below).

The following server parameters for HTTP multiplexing control the size of the connection re-use pool.

• Maximum Reused Connections (An integer specifying the maximum number of reusable connection entries for this server allowed in the reusable server pool. The default is 0, which means that there is no limit on the number of reusable connection pool entries.
  
  If you have HTTP multiplexing enabled and CPU or memory usage on FortiADC is significant, you can use this parameter to limit the size of the reusable connection pool -- which in turn limits the amount of memory and CPU resources used to manage HTTP multiplexing.
  
  You may also want to limit the number of reused connections to a server if the server is experiencing resource issues related to maintaining open connections with FortiADC.
• Reused Connection Timeout (The number of seconds after which a connection record for an idle connection in the reusable connection pool is removed, and the connection closed. The default value is 0 seconds, which means that records in the reusable connections pool never expire.