Ok, thanks let me work around on your ideas, and let you know in couple of days, I really appreciate your prompt replies.
-----Original Message----- From: Dale, Matt [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 25, 2004 6:31 PM To: Tomcat Users List Subject: RE: Tomcat JVM GC You should still look at the articles that I posted my reply. If you really want to use your own garbage collection then you will have to first fix the size of the certain areas within the heap. There is no way to turn off the jvm's own garbage collection, when it cannot allocate space for an object it will do a garbage collection. If there is still not enough space then it will expand the pool so that there is space, up until the maximum allowed for that pool. If you fix the size of the pools and always do a gc before the pool runs out of memory then you will be fine. If you've fixed the pools and you run out of memory then your own gc algorithm must be deficient and the JVM will do a gc anyway. I suspect that with the vast array of GC parameters available you should be able to find some that will work as well as or better than your own but thats just my opinion. -----Original Message----- From: Shakeel Ahmad [mailto:[EMAIL PROTECTED] Sent: 25 August 2004 14:17 To: Tomcat Users List Subject: RE: Tomcat JVM GC Actually we have our own gc mechanism which has a proven record of doing things for our application, it never lets our application go out of memory, but it works at high level, now with this robust design we have only issues from JVM's original gc work. Our calculations have proven that if JVM's gc does not work automatically then our real time nodes can work more effectively. -----Original Message----- From: Mats Henrikson [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 25, 2004 4:46 PM To: Tomcat Users List Subject: RE: Tomcat JVM GC > Its known that JVM schedular runs gc thread depending upon some concrete > values, now I want to set such parameters, or my heap sizes so that the JVM > schedular, ignores gc thread. We have 1.3G Ram on our server and our heap You are mistaken, you do not want it to ignore the gc thread, as you would then very fast run out of heap space, you just want to tune the garbage collector a little. To do this, read this page until you understand it: http://java.sun.com/docs/hotspot/gc1.4.2/ Then you can use the GC Portal tool to help you define the optimal GC configuration for your application: http://java.sun.com/developer/technicalArticles/Programming/GCPortal/ Of course, it could turn out that in order to improve your performance you might have to rewrite parts of your application to be less wasteful with objects. Regards, -- Mats Henrikson Unix Systems Programmer Systems Development & Support Oxford University Computing Services --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
