Originally posted by Peter Johnson:
The memory usage for the java process is more that just the Java heap. It consists of (hope it didn't forget anything):
You left out the code of the JVM itself
You left out ... any local variables.
The best way to tell how an individual process effect memory usage is to terminate the app and see how much free memory increases
Originally posted by Susan Smith:
We have a server where around 100+ console-based java programs running at the same time in a REDHAT linux server (looping continuously).
This may be a bit OT, but I would never expect 100+ java programs to run well. Can you combine them? You have a lot of potential overhead keeping all of them separate.
The best way to tell how an individual process
effect memory usage is to terminate the app and
see how much free memory increases
The client system is optimal for applications which needs fast startup times or small footprints. The server system is optimal for applications where the overall performance is most important