We have this documentation page [1] that explains JVM memory allocation,
although not in much more detail than you already know.
The important part is that you should start monitoring how your memory
grows over time (two suggestions are psi probe and jconsole) and tweak the
values in your JAVA_OPTS accordingly. Also don't forget that the memory
assigned to Tomcat must not exceed total RAM available on the system (you
don't want it to start swapping). Check how much memory you have available
when Tomcat is off (because there are also other services on the system
which require a small amount of memory). Keep some memory unallocated,
otherwise your CLI jobs may start crashing - they have a default of 256 MB
[2], but some tasks may need more.
Ultimately, your periodic problem may be a scheduled job that fails to run
because it doesn't have enough memory allocated. Or it runs and crashes
Tomcat by starving it from memory. Check when your DSpace CLI tasks are
scheduled to run.
[1] https://wiki.duraspace.org/display/DSDOC5x/Performance+Tuning+DSpace
[2] https://github.com/DSpace/DSpace/blob/dspace-4_x/dspace/bin/dspace#L75
Regards,
~~helix84
Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
