Why does Dialog Work Processes in "Waiting" status...

Former Member · ‎05-30-2014

Hi, my name's Denis, and i'm a newbie in the "SAP World".

I will apreciate any help with this doubt.

I'm monitoring a BI productive system, and one of the servers is sending me a warning, that says the actual SWAP is too high.

I started to find out, what was causing the server SWAP more than 70% of the total available.

I found out, that the server had 50% of physical memory still available, so, and i read in some forums, that Linux systems can SWAP at any time, even if there are still physical memory available, something related to the fact, that pages with lowest usage ratio, are moved to the SWAP memory, instead of the real memory-in-cache. I'm right?

2nd: I used the "top" command, and organize the processes by RES column (I think is the aproximate value of real mem. used), and then... by SWAP column.

The results:

by RES

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ SWAP COMMAND

594 bp1adm 20 0 16.8g 3.0g 3.0g S 0.0 19.1 43:59.48 13g BP1_92_DIA_W68

13017 bp1adm 20 0 16.7g 2.6g 2.6g S 0.0 16.8 6:44.15 14g BP1_92_DIA_W15

4910 bp1adm 20 0 17.0g 2.3g 2.2g S 0.0 14.7 47:00.10 14g BP1_92_DIA_W64

25822 bp1adm 20 0 16.8g 2.3g 2.2g S 0.0 14.5 73:35.65 14g BP1_92_DIA_W60

564 bp1adm 20 0 16.8g 2.1g 2.1g S 0.0 13.5 35:50.05 14g BP1_92_DIA_W52

2498 bp1adm 20 0 16.9g 1.9g 1.8g S 0.0 12.1 27:35.53 15g BP1_92_DIA_W33

591 bp1adm 20 0 16.8g 1.9g 1.8g S 0.0 11.9 8:58.00 14g BP1_92_DIA_W65

566 bp1adm 20 0 16.8g 1.8g 1.7g S 0.0 11.2 8:01.49 15g BP1_92_DIA_W54

583 bp1adm 20 0 16.8g 1.3g 1.3g S 0.0 8.4 12:39.27 15g BP1_92_DIA_W57

24904 bp1adm 20 0 16.7g 1.2g 1.2g S 0.0 7.8 1:07.60 15g BP1_92_DIA_W48

598 bp1adm 20 0 16.7g 1.2g 1.2g S 0.0 7.6 11:07.14 15g BP1_92_DIA_W72

27507 bp1adm 20 0 16.8g 1.2g 1.2g S 0.0 7.6 9:23.86 15g BP1_92_DIA_W27

522 bp1adm 20 0 16.8g 1.0g 1.0g S 0.0 6.5 108:50.97 15g BP1_92_DIA_W14

14846 bp1adm 20 0 16.7g 875m 839m S 0.0 5.4 0:39.16 15g BP1_92_DIA_W28

11126 bp1adm 20 0 16.8g 797m 790m S 0.0 5.0 70:29.62 16g BP1_92_DIA_W63

11733 bp1adm 20 0 16.8g 769m 760m S 0.0 4.8 13:18.62 16g BP1_92_DIA_W29

541 bp1adm 20 0 16.8g 676m 663m S 0.0 4.2 15:01.39 16g BP1_92_DIA_W32

10845 bp1adm 20 0 16.8g 669m 650m S 0.0 4.2 13:43.47 16g BP1_92_DIA_W69

30196 bp1adm 20 0 16.8g 646m 626m S 0.0 4.0 110:16.52 16g BP1_92_DIA_W2

547 bp1adm 20 0 16.8g 597m 575m S 0.0 3.7 23:25.30 16g BP1_92_DIA_W36

562 bp1adm 20 0 16.8g 586m 561m S 0.0 3.6 61:51.23 16g BP1_92_DIA_W50

531 bp1adm 20 0 16.8g 556m 544m S 0.0 3.5 30:22.45 16g BP1_92_DIA_W22

13341 bp1adm 20 0 16.7g 529m 516m S 0.0 3.3 8:36.61 16g BP1_92_DIA_W43

2617 bp1adm 20 0 16.8g 509m 491m S 0.0 3.2 20:17.90 16g BP1_92_DIA_W47

521 bp1adm 20 0 16.8g 447m 413m S 0.0 2.8 72:42.43 16g BP1_92_DIA_W13

517 bp1adm 20 0 16.8g 443m 443m S 0.0 2.8 52:37.59 16g BP1_92_DIA_W10

21445 bp1adm 20 0 16.8g 429m 429m S 0.0 2.7 3:43.75 16g BP1_92_DIA_W35

600 bp1adm 20 0 16.8g 426m 409m S 0.0 2.7 29:06.18 16g BP1_92_DIA_W73

561 bp1adm 20 0 16.9g 363m 360m S 0.0 2.3 17:47.65 16g BP1_92_DIA_W49

8879 bp1adm 20 0 16.7g 304m 212m S 0.0 1.9 7:55.55 16g BP1_92_BTC_W104

7012 bp1adm 20 0 16.7g 303m 200m S 0.0 1.9 6:13.91 16g BP1_92_BTC_W84

29639 bp1adm 20 0 16.7g 299m 298m S 0.0 1.9 1:07.64 16g BP1_92_DIA_W41

530 bp1adm 20 0 16.7g 283m 258m S 0.0 1.8 14:24.52 16g BP1_92_DIA_W21

by SWAP

Tasks: 257 total, 1 running, 255 sleeping, 0 stopped, 1 zombie

Cpu(s): 0.0%us, 0.3%sy, 0.0%ni, 99.5%id, 0.2%wa, 0.0%hi, 0.0%si, 0.0%st

Mem: 16464920k total, 14432312k used, 2032608k free, 325812k buffers

Swap: 20971512k total, 15082056k used, 5889456k free, 6103000k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ SWAP COMMAND

548 bp1adm 20 0 16.9g 21m 21m S 0.0 0.1 30:31.87 16g BP1_92_DIA_W37

514 bp1adm 20 0 16.8g 5512 5500 S 0.0 0.0 58:36.72 16g BP1_92_DIA_W7

568 bp1adm 20 0 16.8g 5964 5880 S 0.0 0.0 51:18.23 16g BP1_92_DIA_W56

27960 bp1adm 20 0 16.8g 5760 5756 S 0.0 0.0 191:32.90 16g BP1_92_DIA_W19

510 bp1adm 20 0 16.8g 5876 5856 S 0.0 0.0 32:53.76 16g BP1_92_DIA_W3

516 bp1adm 20 0 16.8g 5848 5832 S 0.0 0.0 5:16.66 16g BP1_92_DIA_W9

527 bp1adm 20 0 16.8g 4856 4760 S 0.0 0.0 6:24.89 16g BP1_92_DIA_W18

601 bp1adm 20 0 16.8g 5968 5912 S 0.0 0.0 28:29.13 16g BP1_92_DIA_W74

535 bp1adm 20 0 16.8g 5900 5860 S 0.0 0.0 31:58.94 16g BP1_92_DIA_W26

551 bp1adm 20 0 16.8g 4700 4680 S 0.0 0.0 4:20.26 16g BP1_92_DIA_W40

596 bp1adm 20 0 16.8g 5876 5804 S 0.0 0.0 11:07.72 16g BP1_92_DIA_W70

557 bp1adm 20 0 16.8g 2960 2920 S 0.0 0.0 10:07.54 16g BP1_92_DIA_W45

550 bp1adm 20 0 16.8g 5820 5764 S 0.0 0.0 13:22.18 16g BP1_92_DIA_W39

529 bp1adm 20 0 16.8g 4516 4428 S 0.0 0.0 15:38.11 16g BP1_92_DIA_W20

565 bp1adm 20 0 16.8g 5900 5876 S 0.0 0.0 25:49.62 16g BP1_92_DIA_W53

661 bp1adm 20 0 16.8g 27m 27m S 0.0 0.2 17:05.59 16g BP1_92_DIA_W16

508 bp1adm 20 0 16.8g 5736 5720 S 0.0 0.0 1:52.36 16g BP1_92_DIA_W1

515 bp1adm 20 0 16.8g 5952 5892 S 0.0 0.0 15:57.61 16g BP1_92_DIA_W8

545 bp1adm 20 0 16.7g 2888 2868 S 0.0 0.0 1:35.73 16g BP1_92_DIA_W34

540 bp1adm 20 0 16.8g 5984 5920 S 0.0 0.0 13:44.17 16g BP1_92_DIA_W31

553 bp1adm 20 0 16.7g 2972 2896 S 0.0 0.0 9:15.90 16g BP1_92_DIA_W42

558 bp1adm 20 0 16.8g 27m 27m S 0.0 0.2 11:28.38 16g BP1_92_DIA_W46

507 bp1adm 20 0 16.7g 4156 4084 S 0.0 0.0 5:54.58 16g BP1_92_DIA_W0

563 bp1adm 20 0 16.7g 2752 2724 S 0.0 0.0 1:45.77 16g BP1_92_DIA_W51

534 bp1adm 20 0 16.7g 2812 2800 S 0.0 0.0 2:19.12 16g BP1_92_DIA_W25

11135 bp1adm 20 0 16.7g 5800 5772 S 0.0 0.0 1:28.36 16g BP1_92_DIA_W55

10348 bp1adm 20 0 16.7g 12m 12m S 0.0 0.1 2:37.09 16g BP1_92_BTC_W91

32157 bp1adm 20 0 16.7g 5780 5756 S 0.0 0.0 12:59.49 16g BP1_92_DIA_W24

10069 bp1adm 20 0 16.7g 4208 4140 S 0.0 0.0 1:52.20 16g BP1_92_DIA_W4

17430 bp1adm 20 0 16.8g 56m 55m S 0.0 0.3 2:49.53 16g BP1_92_BTC_W102

593 bp1adm 20 0 16.8g 27m 27m S 0.0 0.2 19:10.09 16g BP1_92_DIA_W67

28616 bp1adm 20 0 16.7g 4800 4748 S 0.0 0.0 0:19.61 16g BP1_92_DIA_W71

549 bp1adm 20 0 16.7g 3112 3104 S 0.0 0.0 1:17.51 16g BP1_92_DIA_W38

I want to know:

BP1_92_DIA_W68 - means "Work Process 68, Dialog type, on BP1_92"?

If positive, i already search for this process, and others on the top of memory utilization, and they are in "Waiting" status. (i also have checked the PID, its the same)

So, why does Dialog Work Processes in "Waiting" status, are consuming too much memory?

Thanks guys

Former Member · ‎05-30-2014

Very simply put, Abap work processes primarily use shared memory, but can also acquire private memory, if shared memory is not available. They keep the private memory reserved until they are restarted. If a (configurable) threshold of private memory is reached, they automatically restart to release that memory.

You might want to spend some time investigating in transaction ST02. It shows you, among other things, how much shared (extended) and private (heap) memory is consumed. It also shows you the history of those values as well as the related profile parameters to tweak.

The questions I would ask myself to begin with are:

Are processes frequently acquiring heap memory?
If the answer is no, then maybe you just have too many work processes for the server's capacity?
If the answer to #1 is yes, is the threshold for a work process restart maybe set too high, or is the size of shared memory in total and/or its allowance per process too low?

ashish_vikas · ‎05-30-2014


So, why does Dialog Work Processes in "Waiting" status, are consuming too much memory?

DIA work process in Waiting status means this process is Free and just waiting for any work.

Status

Current status of the work process. Possible statuses are:

Running (executing a request)
Waiting (idle and waiting for a request)
Hold (held for one user) is not an abnormal state, but a work process can only serve a single user.
If too many processes are in Hold, then system performance suffers. You can then use the Reason field to identify holds that perhaps can be released.
Stopped (aborted; Restart set to No).
Shutdown: Process terminated because of a shutdown
For more information, see SAP Application Server States
Reserved: Process is reserved
For more information, see Dynamic Work Processes

http://help.sap.com/saphelp_nwpi711/helpdata/en/46/fb763b6d4c5515e10000000a1553f6/content.htm

best regards

ashish

Why does Dialog Work Processes in "Waiting" status, are consuming too much memory? (1GB~3GB)

Accepted Solutions (0)

Answers (2)

Answers (2)

Re: "Failed to update setup engine executables. Pr...

Re: Timer showing while sending the mails from SAP

Re: Best practice to connect to multiple databases...

SAP Hana Calculation view input parameter from JPA...

Re: Adaptation error in sap mdg ui screen customer