Provide data to help improve applications in QA and production
Determine which process causes the issue.
System>Server Settings> Server Monitoring>Open Server Monitoring
Check Memory/CPU/Disk usage.
Check spikes. Identify which process is causing the issue. (When you restart server, normally the usage will be high.)
Execute the garbage collector (You could execute it once in a while for maintenance)
If Java Melody usage is high, click Execute the garbage collector in System information.
Clear all caches. Click Details in a Data cache section>Scroll down>Clear all caches
Send a Javamelody PDF report to support. Select Period. Click a PDF icon
java.lang.OutOfMemoryError. If there is an error in ContentManager.log such as java.lang.OutOfMemoryError: Java heap space or java.lang.OutOfMemoryError: PermGen space,
Execute the garbage collector.
Check errors in logs.
Find memory leaks.
Tune Content Manager and check Tomcat Java Memory settings. (Initial memory pool and Maximum memory pool)
Increase memory.
check Tomcat Java Memory Settings. (Initial memory pool and Maximum memory pool)