Generating garbage at a slower rate might be good, but having a 2 second GC surprises me, and suggests that the default heap parameters are inappropriate. "Improving Java[tm] Application Performance and Scalability by Reducing Garbage Collection Times and Sizing Memory Using JDK 1.4.1" runs through the gory details as well as having a link to a useful tool for analysing garbage collection data [-verbose:gc, -Xloggc:<file> etc].
http://wireless.java.sun.com/midp/articles/garbagecollection2/ Note also that the Server JVM can use different algorithms and parameters than the Client [default] JVM. It certainly made a huge difference on a multithreaded application I was investigating the performance of. Garbage was generated at greater than 200MB/s but cleaned up very efficiently once the heap was appropriately configured. ============================================================================ ,-_|\ Richard Smith - SE Melbourne / \ Sun Microsystems Australia Phone : +61 3 9869 6200 [EMAIL PROTECTED] Direct : +61 3 9869 6224 \_,-._/ 476 St Kilda Road Fax : +61 3 9869 6290 v Melbourne Vic 3004 Australia =========================================================================== =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
