I’m going to ask the question posed in RequestTimeout in a different way…
I’m working in a large environment that is periodically experiencing heavy loads. The referenced post suggests dodges the value of RequestTimeout and suggests adding more policy servers. Realizing it’s not possible to recommend an optimal value of RequestTimeout to suit all situations, I would appreciate some feedback on the following:
- Assume the environment has adequate capacity to service requests for all but the busiest hour of the week. What is an appropriate methodology for tuning RequestTimeout? I can think of two ways to do this:
- Increase RequestTimeout a significant amount from the default of 60 to, say 120. Observe results at 120 and reduce RequestTimeout 10 seconds at a time until the “optimal” value is determined. Is there an upper limit to RequestTimeout that you would consider unreasonable?
- Increase RequestTimeout in 10-second increments and stop when connections are no longer timing out under heavy load.
- Do you have any anecdotes to share regarding the circumstances and results when you tuned RequestTimeout in an enterprise environment?
Source: New feed
{pubDate}