cancel
Showing results for 
Search instead for 
Did you mean: 

SM66.

Former Member
0 Kudos

Hi All,

If a work process comes in PRIV mode wat r the steps to perform.

& Wat is there to check in Workload Analysis.(ST03).

Thanks & Regards.

Syed.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello Syed,

In the Workload Monitor, you have check the following:-

The following values normally indicate good performance:

• Average roll-in time < 20 ms

• Average roll wait time < 200 ms

• Average load (and generation) time < 10 % of response time (<50 ms)

• Average database request time < 40 % of (response time - wait time)

• Average CPU time < 40 % of (response time - wait time)

• Average CPU time Not much less than processing time

Well there is much more to dig into ST03n depends on your know how and requirements.

Hope this will help you.

Regads,

Jafer

Former Member
0 Kudos

Hello Syed ,

Due to high memory requirements or a lack thereof, several work processes are moved to available extended memory in the PRIV mode.

Only work process-local memory (heap) is allocated instead of extended memory so that the user context roles no longer occur; the work process in question is assigned exclusively to the user instead.

A work process is available in the DEBUG mode and a user is exclusively assigned as a result; however, the user is not active for a longer time.

Therefore, with an increasing number of work processes assigned exclusively to a user, there is a risk of the average response time deteriorating because work processes assigned exclusively to other users is no longer available.

To avoid this problem,

1 )The maximum number of work processes, which must be in the PRIV mode longer than a specific period of time or inactivein the DEBUG mode, is limited.

This behavior is controlled by the following profile parameters:

1 )rdisp/max_priv_time # Standard value: 600

2 )rdisp/wppriv_max_no # Standard value: MAX(1, Anzahl Dialog-WPs)

3 )rdisp/max_debug_lazy_time # Standard value: 600

If there are more than rdisp/wppriv_max_no work processes longer than rdisp/max_priv_time seconds in the PRIV mode, the work process contained the longest in the PRIV mode is cancelled as long as the maximum rdisp/wppriv_max_nowork processes are longer than rdisp/max_priv_time in the PRIV mode.

Using the rdisp/max_debug_lazy_time parameter, you can define the maximum time a debugging session may be lazy, that is, interaction with the debugger must not occur before it is automatically reset by the system.

Regards ,

Santosh Karadkar