Razuna takes up to 300G of RAM -_-

Razuna v2 Legacy Self-Hosted
1

Hi,

I noticed a very high amount of comitted RAM of our Razuna installation.
In “idle mode” (when not that much happens) it takes 80G ram, when uploading images and creating the renditions it jumps up to 300G (see attached image).

I tried to stick close to your wiki (http://wiki.razuna.com/display/ecp/Adjusting+Memory+Settings+for+Tomcat and http://wiki.razuna.com/display/ecp/Configure+Tomcat+for+production+deployment ) so my line in setenv.sh is:

CATALINA_OPTS="$CATALINA_OPTS -server -Xss1G -Xms4G -Xmx4G -Djava.awt.headless=true -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -XX:+PrintGCDateStamps -XX:-OmitStackTraceInFastThrow -Djava.security.egd=file:/dev/./urandom"

Anyone can explain what’s happening? The VM where it’s running has 16G of RAM, the host has 192G overall.

Is it a normal behaviour or should I adjust something?
Please advise.

2

Please go to Administration for your Razuna , try to clear database and template cache.

Then re-check again to see how.

Thanks

3

Did that. I also changed the parameters in setenv to

CATALINA_OPTS="$CATALINA_OPTS -server -Xss512M -Xms2G -Xmx4G -Djava.awt.headless=true -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -XX:+PrintGCDateStamps -XX:-OmitStackTraceInFastThrow -Djava.security.egd=file:/dev/./urandom"

It results in this…

Now it uses less virtual memory (“committed ram”) and uses more cache in real ram.

Weird.

4

Sorry to hear of your issues. Though, I doubt that we can be of any help.

We are running multiple (300+ servers) of Razuna. Many with 32GB or 64GB
RAM. None of those servers show an issue like you describe. I doubt that
this is a Razuna issue and would look further into your overall
configuration. If this is a virtual machine, I recommend to look into the
VM settings some more.

Hope this helps.

5

Just to give an explanation:

That huge virtual (“committed”) ram is a java issue. It’s reserving such an amount for no reason, furthermore it’s never using it. It’s just kinda “virtual” request so it’s ok to ignore that value.

Case can be closed.