|
|
|
When the Web Agent requires additional sockets from the connection pool during peak loads, the NewSocketStep parameter determines the number of sockets obtained each time.
If the value of the NewSocketStep parameter is set too low, response time during peak periods suffers because the Web Agent takes extra time to create socket connections.
To help avoid slow response times, use your capacity planning estimates to determine how many requests your Web Agents handle, and then increase the value of the NewSocketStep parameter accordingly.
The ideal number for this parameter is one large enough to prevent the Web Agent from spending too much time creating sockets for requests as the load on the web server increases.
We recommend experimenting with different settings until you find what works best in your SiteMinder environment.
Note: For multiprocess web servers (such as an Apache-based server in pre-fork mode), you can reduce this number of sockets to one. Because each process uses only a single thread to communicate with the SiteMinder Policy Server, only one socket is required.
| Copyright © 2010 CA. All rights reserved. | Email CA about this topic |