SPM is consuming huge memory

[Venkata_Reddy_K]

Hi All,

Good day to you.

We have installed wM 9.9 on Linux ( 8 GB RAM , 2 CPU ) . we have 4 such machines.

On each server we have installed different products as below

1. IS , UM , SPM
2. IS , UM , SPM
3. Terracotta, MWS , SPM
4. CCE, CTP, UM, SPM

Now are facing an issue on each box with SPM as it is consuming huge memory literally more than 50% due to which some of the products are going unresponsive.

In general SPM can run with 128 MB memory as per my knowledge. But why is it consuming lot of memory.

We have installed all the latest fixes in each server.

Can anyone help me to resolve this.

Regards,
Venkat.

[Sergei_Pogrebnyak]

Hi,
The best way to answer this question is to create memory dump of the SPM process, open SI with SAG support and provide the dump file with SPM logs for analysis

Thanks
Sergei

[Ivan_Herlambang1 (Ivan Herlambang)]

Hello,

Perhaps you could modify your JVM Options add the option:
-XX:MaxMetaspaceSize=[the size of memory to be allocated]

BUT

A better explanation about [google]java metaspace[/google] can be found or in stackoverflow

Mattias Jiderhamn

The main difference from a user perspective - which I think the previous answer does not stress enough - is that Metaspace by default auto increases its size (up to what the underlying OS provides), while PermGen always has a fixed maximum size. You can set a fixed maximum for Metaspace with JVM parameters, but you cannot make PermGen auto increase.

ankur-singhal

In Simple words
Since the class metadata is allocated out of native memory, the max available space is the total available system memory. Thus, you will no longer encounter OOM errors and could end up spilling into the swap space.

The removal of PermGen doesn’t mean that your class loader leak issues are gone. So, yes, you will still have to monitor your consumption and plan accordingly, since a leak would end up consuming your entire native memory.

Conclusion:
If you set the parameter -XX:MaxMetaspaceSize you could get OutOfMemory, but if you do not set this parameter you can get the process allocate all the machine memory (including swap space). So use with caution!!

N.B: This happened because wM using Java 8