Tuning ODR persistent connections

Tune the persistent connection settings for ODR performance to minimize the time you spend setting up new connections and taking down older connections during a barrage of requests. Primarily, this tuning is relevant to the connections between the ODR and the application servers.

Before you begin

Modify your JVM heap settings. For more information about the JVM settings, read about modifying the JVM heap size for the on demand router.

About this task

Adjust the application server's number of persistent requests so that the ODR reuses the connection to the application server for as long as it can. To do this, configure the ODR transport chain to tune inbound connections to the ODR. To tune outbound connections from the ODR, configure the transport chains of the application servers that are members of a dynamic cluster. To do so, configure the transport chain of the dynamic cluster from within the dynamic cluster server template. Changes to the dynamic cluster's server template are automatically applied to all cluster members.

You should set number of persistent requests high enough to avoid having to bring down and recreate a connection during a barrage of requests, so set the value to at least the number of requests in a single barrage of request. The barrage can be a single page with associated data with a long think time, or a series of pages and associated data in short succession. Setting a value higher than the number of requests in a single barrage of request will not negatively affect performance provided the persistent timeout is set appropriately to close idle connections.

Procedure

Tune the ODR's HTTP_PROXY_ADDRESS and HTTPS_PROXY_ADDRESS transport chains.
In the administrative console, click Servers > Server types > On demand routers > odr_name > Ports.
1. Click View associated transports for the port whose transport chains you want to view.
2. Click transport_chain_name.
3. Click HTTP inbound channel.
4. Ensure that Use persistent (keep-alive) connections is checked.
5. Specify an unlimited number of persistent requests per connection.
  Select Unlimited persistent requests per connection.
6. Specify a maximum number of persistent requests per connection.
  Select Maximum persistent requests per connection. Setting this value to -1 yields the best performance.
7. Click Apply and OK to save your changes.
Tune the application servers' HTTP_PROXY_ADDRESS and HTTPS_PROXY_ADDRESS transport chains.
In the administrative console, click Servers > Clusters > Dynamic clusters > dynamic_cluster_name > Server template > Web container settings > Web container transport chains.
1. Configure the WCInboundDefault transport chain.
  1. Click WCInboundDefault.
  2. Click HTTP inbound channel.
  3. Ensure that Use persistent (keep-alive) connections is checked.
  4. Specify an unlimited number of persistent requests per connection. Select Unlimited persistent requests per connection.
  5. Specify a maximum number of persistent requests per connection. Select Maximum persistent requests per connection, and set the value to -1. This allows an infinite number of requests to flow over a single connection. Connections that are not used for an extended period of time are still closed due to the inactivity timeout for the connection.
  6. Click Apply and OK to save your changes.
2. Configure the WCInboundDefaultSecure transport chain.
  1. Click WCInboundDefaultSecure.
  2. Click HTTP inbound channel.
  3. Ensure that Use persistent (keep-alive) connections is checked.
    - Select Unlimited persistent requests per connection to specify an unlimited number of persistent requests per connection.
    - Select Maximum persistent requests per connection to specify a maximum number of persistent requests per connection. Setting this value to -1 yields the best performance.
  4. Click Apply and OK to save your changes.