Right, thanks. That makes a bit more sense now.
Currently, Glassfish is using 1.2GiB after running a few deploy/undeploy cycles (I haven't even been to a webpage yet!), and JConsole reports that ~215MiB of Heap is committed, and ~200MiB of non-heap space.
Which brings up my next question: Why is Glassfish using up so much RAM? What is it I'm doing that makes Glassfish / Java / Linux decide to allocate more memory?
[Message sent by forum member 'ipsi']
http://forums.java.net/jive/thread.jspa?messageID=469070