cancel
Showing results for 
Search instead for 
Did you mean: 

Memory utilization is very high in Netweaver 2004S

former_member201800
Participant
0 Kudos

Hi All,

We are noticing very high memory utilization in our Dev system.

While checking, i found that the spool request was very high on this system (more then 27k). I have deleted all the spool request, even though there is no changes in utilization. There is hardly 1 or 2 BTC/DIA are running.

At OS level, i found that 6 instances of Jaunch are running. 2 Jlaunch processes are taking 3.76 GB.

Please suggest, how to bring down the memory utilization.

With Regards,

Shyam Kumar

Accepted Solutions (0)

Answers (1)

Answers (1)

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello

2 Jlaunch processes are taking 3.76 GB.

Open Configtool andcCheck the value for Heap Memory (Xmx and Xms) for the server nodes.

Cheers

RB

former_member201800
Participant
0 Kudos

Hi Reagan,

It's value is 1024 MB. Total heap size is also 1024 MB.

------------------------------------------------------------------------------------------------------------------------------------------------------

                                                                     PROCESS LIST                                                         Users=    3

                         User      CPU %    Thrd Disk        Memory       Block

Process Name     PID     Name   ( 200% max) Cnt  IOrate      RSS/VSS      On

--------------------------------------------------------------------------------

jlaunch            22340 db1adm       31.3   237  37.5    2.40gb   3.45gb   PRI

kmemdaemon             6 root         20.3     3   0.0     192kb    216kb SLEEP

vhand                  2 root         13.1     1 141.7      64kb     72kb SLEEP

bpbkar32            1082 root          9.7     6  95.7    13.7mb   57.8mb    IO

oracleDB1          22397 oradb1        5.5     1  13.2    76.8mb   85.8mb SOCKT

vxfsd                 79 root          4.7    15  20.7    22.2mb   25.0mb SLEEP

fcachedaemon          68 root          2.7     2   0.0     128kb    144kb SLEEP

ora_j000_DB1       22400 oradb1        2.1     1  35.9    70.5mb   80.1mb   new

cimprovagt         15002 root          0.6    12  79.4     1.3mb   34.5mb SLEEP

java               21326 db1adm        0.4    24   0.1    15.8mb   1.49gb SLEEP

dw.sapDB1_DV       16883 db1adm        0.2     1   0.9   108.9mb  349.6mb   SEM

jlaunch            22339 db1adm        0.2   119   0.1   280.7mb  893.5mb SLEEP

ora_smon_DB1       28754 oradb1        0.0     1   0.3    73.2mb   96.1mb SLEEP

ora_q000_DB1       28777 oradb1        0.0     1   0.5    74.2mb   89.7mb SLEEP

dw.sapDB1_DV       16085 db1adm        0.0     1   0.0   120.2mb  383.0mb   SEM

ora_mmnl_DB1       28762 oradb1        0.0     1   0.1    73.6mb   83.3mb SLEEP

oracleDB1          22373 oradb1        0.0     1   0.0    75.1mb   86.8mb SOCKT

ora_mman_DB1       28746 oradb1        0.0     1   0.1    73.3mb  330.9mb SLEEP

oracleDB1          16890 oradb1        0.0     1   0.0    82.8mb   98.1mb SOCKT

oracleDB1          22386 oradb1        0.0     1   0.0    75.3mb   87.2mb SOCKT

oracleDB1          16087 oradb1        0.0     1   0.0    75.7mb   96.3mb SOCKT

ora_psp0_DB1       28744 oradb1        0.0     1   0.1    73.3mb  330.9mb SLEEP

ora_arc0_DB1       28767 oradb1        0.0     1   0.1    73.9mb  100.0mb SLEEP

dw.sapDB1_DV       20891 db1adm        0.0     1   0.0   101.3mb  349.4mb   SEM

httpd              20034 hpsmh         0.0    27   0.0    49.1mb  170.1mb SLEEP

dw.sapDB1_DV       16886 db1adm        0.0     1   0.0   116.9mb  348.9mb   SEM

oracleDB1          22369 oradb1        0.0     1   0.0    75.3mb   86.8mb SOCKT

ora_pmon_DB1       28742 oradb1        0.0     1   0.0    73.4mb  333.0mb SLEEP

oracleDB1          19826 oradb1        0.0     1   0.0    80.0mb   94.1mb SOCKT

dw.sapDB1_DV       18412 db1adm        0.0     1   0.0   113.3mb  365.4mb   SEM

dw.sapDB1_DV       15936 db1adm        0.0     1   0.0   100.5mb  348.9mb   SEM

dw.sapDB1_DV       16882 db1adm        0.0     1   0.0   116.9mb  348.9mb   SEM

oracleDB1          16898 oradb1        0.0     1   0.0    81.7mb   92.3mb SOCKT

dw.sapDB1_DV       16804 db1adm        0.0     1   0.0   117.9mb  383.0mb   SEM

dw.sapDB1_DV       16884 db1adm        0.0     1   0.0   105.9mb  365.6mb   SEM

dw.sapDB1_DV       16416 db1adm        0.0     1   0.0   110.7mb  365.5mb   SEM

oracleDB1          16894 oradb1        0.0     1   1.1    74.5mb   91.6mb SOCKT

dw.sapDB1_DV       10335 db1adm        0.0     1   0.0   113.3mb  383.0mb   SEM

dw.sapDB1_DV       19960 db1adm        0.0     1   0.0   110.4mb  349.4mb   SEM

ora_dbw0_DB1       28748 oradb1        0.0     1   6.1    73.5mb  116.8mb SLEEP

oracleDB1          22362 oradb1        0.0     1   0.0    74.8mb   94.1mb SOCKT

oracleDB1          22376 oradb1        0.0     1   0.0    75.0mb   86.8mb SOCKT

oracleDB1          16896 oradb1        0.0     1   0.0    89.4mb  101.0mb SOCKT

cimservermai       11554 cimsrvr       0.0    23   0.0    26.4mb   91.8mb SLEEP

With Regards,

Shyam

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

Good Day Shyam

You have a dual stack system.

The problem so far looks like the system is not properly configured.

As you have a Java stack you need to always make sure there is sufficient memory on the box.

If the server is short of memory then you need reduce the memory assignment for the Oracle database and for the ABAP stack (IF POSSIBLE).

There is no point in increasing memory parameters when you dont have sufficient memory of the machine especially when you have a Java stack.

Run this command as root and you will get the top 5 memory consuming processes.

ps -elf | sort -k 10n | tail -5

If there is performance problem then you need to check the server0 trace files to check the frequency of garbage collection.

Also check whether there are heapdumps generated in the server0 directory.

You can use the MAT tool to analyse the dump.

Also check the JRE you are on and update it to the latest JRE or SAPJVM.

If there is nothing much you can do then I suggest to you schedule regular restart of the system (with cleaning of Shared Memory) to avoid these issues.

Cheers

RB