DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=31760>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31760 Handle / Semaphore Leak? ------- Additional Comments From [EMAIL PROTECTED] 2004-10-24 10:00 ------- Yesterday I made a comparison of Java 1.4.2_06 and 1.4.2_05 with Cocoon2.1.5.1 and Tomcat 5.0.27. With 1.4.2_06, I tested different Xmx and Xms settings. VM Time Handles RAM VM-Args ------------------------------------------------------------ a) 1.4.2_05: 8h 5579 45Mb -Xmx300m b) 1.4.2_06: 8h 5179 46Mb -Xmx300m c) 1.4.2_06: 8h 44522 336Mb -Xms300m -Xmx1000m Sometimes there was no increasing for a while (e.g. 15min) and after this pause it was increasing again. The test b witch seemed to be stable at 3500, now is at 5179. Today I tested Cocoon 2.1.6dev using Jetty: VM Time Handles RAM VM-Args ------------------------------------------------------------ d) 1.4.2_05 4h 12461 69Mb e) 1.4.2_06 4h 12101 59Mb There are no differences between the Java-Versions. Test b and c looks like that the -Xm* settings are deciding about the speed or/and the amount. That's the behaviour described by Michael Straessle. I have no idea why test d and e has the double of amount at the half of time compared to a and b. I am sure the default -Xmx is lower than 300m. Can anybody interpret/comment these results?
