If a dialog work process has used up the roll area assigned to it and the extended memory, private memory is assigned to the work process. The work process goes into PRIV mode (private). In the parameter settings, ensure that not too many dialog work processes are simultaneously in the PRIV mode, since this lowers system performance. If too many dialog work processes run in the PRIV mode in an SAP application server, performance problems arise. The normal processing of user inquiries is slowed down by the PRIV mode work processes.
The SAP System offers a mechanism that lets you terminate non-active dialog processes in the PRIV mode. This mechanism helps reduce performance problems.
1. As an example, your SAP system has 10 dialog work process per instance. By default, the maximum number of work process in PRIV mode to set to 5 at parameter rdispwppriv_max_no in transaction code RZ10.
2. Then, adjust the parameter rdisp/max_priv_time. The parameter is used to set the maximum hold time for work process in PRIV mode. By default, the time is set 600 seconds (10 minutes).
3. So, the situation will become like this, the SAP system will periodically check if more than 5 work process is in PRIV mode after 600 seconds (10 minutes). If the SAP system detected there are more than 5 work process is in PRIV mode, the SAP system will automatically terminate the PRIV mode that has been in the longest time.
