WIS_CLIENT_IDLE_PERIOD

Draft comments: This parameter is being deleted as a result of the implementation of CR16908

Section

WQS

Initial Value

250

Units

Milliseconds

Range

>0

Description

The minimum period (in milliseconds) that the WIS will wait to service client requests before checking for background work. If a client request is received then the period is reset, up to the maximum of WIS_RPCSERVICE_PERIOD.

Tuning

The value of this setting depends on the system profile but it should never be greater than WIS_RPCSERVICE_PERIOD as this is the longest period a WIS will respond to user requests for. The best way to think of this setting is as the minimum time a WIS will spend responding to user requests, as if there are no users logged in the WIS will still wait for WIS_CLIENT_IDLE_PERIOD before continuing to process new messages.Do not set this value too low on systems with a large number of WIS processes. This can cause the WIS processes to continually keep waking up as there are no user requests coming in which there is also no mbox. This can cause a great deal of system activity while not actually performing any work.On live systems with high numbers of user requests, this parameter has little effect as requests are likely to be coming in too frequently. Setting this value to ½ or a ¼ of WIS_RPCSERVICE_PERIOD can help the WIS to process messages during quiet periods if there is a backlog.During bulk load scenarios with no or few users logged in, set WIS_CLIENT_IDLE_PERIOD low (100-200) to ensure that the maximum time is spent processing Mbox instructions.

Related Parameters

WIS_MAXFILEDESC, WIS_TOUT_GRANULARITY, WIS_MBOX_WORK_LIMIT.