config load-balance connection-pool
Use this command to configure connection pool settings.
A connection pool enables Layer 7 load balancing virtual servers to “reuse” existing TCP connections. In the same way that persistent HTTP connections allow a single HTTP connection to retrieve multiple objects, TCP multiplexing allows the virtual server to use a single connection between FortiADC and the backend servers for multiple sessions. Using this connection pool can reduce the impact of TCP overhead on web server and application performance.
Before you begin:
• You must have read-write permission for load balancing feature settings.
After you have created a connection pool configuration, you can specify it in a virtual server configuration.
Note: The feature is not supported for profiles with the Source Address option enabled.
Syntax
config load-balance connection-pool
edit <name>
set age <integer>
set reuse <integer>
set size <integer>
set timeout <integer>
next
end
age | Maximum duration of a connection in seconds. The recommended value is 3000. |
reuse | Maximum number of times that the virtual server can reuse the connection. The recommended value is 2000. |
size | Maximum number of connections in the connection pool. The recommended value is 0, which specifies that there is no limit on the connection size. |
timeout | Maximum number of seconds a connection can be idle before the system deletes it. The recommended value is 30. |
Example
FortiADC-VM # config load-balance connection-pool
FortiADC-VM (connection-pool) # edit lb-connection-pool
Add new entry 'lb-connection-pool' for node 1698
FortiADC-VM (lb-connec~i) # get
size : 10000
age : 86400
reuse : 10000
timeout : 50
FortiADC-VM (lb-connec~i) # set age 3000
FortiADC-VM (lb-connec~i) # set reuse 2000
FortiADC-VM (lb-connec~i) # set size 0
FortiADC-VM (lb-connec~i) # set timeout 30
FortiADC-VM (lb-connec~i) # get
size : 0
age : 3000
reuse : 2000
timeout : 30
FortiADC-VM (example-connec~i) # end