Work process

[former_member799394]

Why does the dialogue work process goes to private mode why not batch work process? can you please tell me the reason...

[jmodaal]

Hello,

a DIA work process switches to PRIV mode (beside a currently running debug session) when exceeding a limit regarding memory consumption and some "local" memory was assigned. Having a look on the work process in SM04 should give some further information regarding the consumed memory.

DIA work processes are shared between the active users, using user context switches (don't know if this is really the right term), whereas batch work processes belong to the job for the whole job lifetime anyways, without any context switching.

[dasistdochscheisse]

when a DIA process goes into PRIV mode, it uses heap memory, ztta/roll_extension is the quota for a DIA process in the extended memory (EM), after that, as said before, it uses heap mem. Heap mem cannot be shared among work processes, EM can. Another reason could be that the total amount of EM is exhausted and a DIA process needs more memory.

Batch processes start with using heap. If the quota is exhausted, it starts using EM.. But it is in PRIV mode from the beginning. Which is ok, the btc process is occupied for the whole runtime of a job, no need to share the memory to other btc processes.

Batch: Heap -> EM
DIA: EM -> HEAP

RSMEMORY shows the current quota for DIA and BTC and the quotas can be temporarily changed here.

[qwertie]

seems like your workprocess reached the limit of the extended memory or like Ulf mentioned you reached the limit of ztta/roll_extension

further details you can find for example here on help.sap.com

https://help.sap.com/saphelp_nw73/helpdata/en/49/32f2b4e92e3504e10000000a421937/content.htm?no_cache...

br

[raquel_gomez]

Hi sravani reddy,

Regarding the meaning of the PRIV mode:
If a DIA work process has used its quota of Extended Memory (EM) or all EM has been used up by all the other work processes; then, the work process starts to allocate HEAP memory (this means that the work process enters into PRIV mode). Therefore, the PRIV mode results either from the lack of total Extended Memory on the server (EM) or because the EM memory quota of that single work process has been reached.

- If one single work process enters into PRIV mode, it means that this particular work process is allocating too much memory.
It already consumed its EM quota and then it started to allocate Heap quota; entering into PRIV mode.

- On the other hand, if there are many work processes entering into PRIV mode on same instance, this may indicate that total Extended Memory has been exhausted.
As none of them have enough EM to allocate, all of them need to start taking Heap memory. Thus, you'll find many work processes on PRIV mode.

When work process enters into PRIV mode, this means that the last user is permanently using this work process and does not release it, because the heap memory is work process local memory and therefore not accessible from other work processes. This goes against DIA work processes uses, but does not affect in case of BTC work processes (where long jobs may be executed).

In general, DIA work processes allocate first EM and then HEAP; while BTC work processes allocate first HEAP then EM. This depends on the Operating System.

Regards,
Raquel