This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Well, it looks like your particular JVM is doing partial cleanups in between full cleanups. However Sun did not actually write all the JVMs and the JVM specs leave quite a bit of room as to how the gc function can be done. Including what messages are spurted out.
"JavaRanch, where the deer and the Certified play" - David O'Meara
The line [GC 1814K->1398K(1984K), 0.0004230 secs] means GC ran for .0004230 sec and reduced the amound of heap memory used from 1814 KB to 1398 KB. Currently 1984 KB are allocated for the heap, though that's not necessarily the maximum possible. If memory use gets too high and GC can't reduce it enough, the JVM will request more from the OS. As long as the OS has memory available, heap size may increase up to the limit set by the -Xmx option. At least, that's how it works for SDK 1.4 on Windows - may be different for other JVM's. [ June 27, 2002: Message edited by: Jim Yingst ]
"I'm not back." - Bill Harding, Twister
Joined: Jan 13, 2002
Thx Cindy and Jim for your answers, it helped me a lot!