[Building Sakai] Sakai memory

[Jon Wheat]

Garbage collection, hmmm, thanks.  Not being a java guy, that helps focus my efforts. 
I'll take a look into the production data as well to see how I can tune the JVM. 

-Jon

>>> "Berg, Alan" <A.M.Berg at uva.nl> 12/8/2010 4:08 PM >>>

100 % CPU sounds like full Garbage Collects. You can see it either via using JMX or setting JAVA_OPTS to include logging.

There is production data in Jira where a number Organisations have set their JAVA_OPT settings as well.
I refer you to Anthony Whytes e-mail on the 24 th November

http://old.nabble.com/-Announcements--Tracking-Sakai-2x-CLE-deployments-%28add-update-your-Jira-PROD-record%29-p30292545.html

For example: http://jira.sakaiproject.org/browse/PROD-4



Alan

Alan Berg
QA Director - The Sakai Foundation

Senior Developer / Quality Assurance
Group Education and Research Services
Central Computer Services
University of Amsterdam

http://home.uva.nl/a.m.berg 


From: sakai-dev-bounces at collab.sakaiproject.org [sakai-dev-bounces at collab.sakaiproject.org] on behalf of Jon Wheat [jwheat at messiah.edu]
Sent: 08 December 2010 20:10
To: Sakai Developers
Subject: [Building Sakai] Sakai memory



Have a question for you all - 
Our Sakai box has 4G of RAM - we have approx 3000 students, and it gets used constantly - to the point we have a  no window to do upgrades without having to alert everyone (and still they get upset when its down for a little bit). 


That said - what is the recommended amount of memory?  I'm thinking 4G is way too little. 


Watching 'top' I see the java cpu process hit 100% then back down, then up in the 80s and back. When this happens, is this a memory problem or something else more serious? 


guess that's two questions. 


thanks, 
-Jon 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101209/e636ae61/attachment.html