Hi, In TomCat's source code, I notice it recycles objects (e.g. RequestBase, StandardSession). But in Sun's documentation, with HotSpot Virtual machine, pooling objects will hinder performance (see below). Could someone please tell me are there advantages of using object pooling in TomCat?
Thank you. Sam <<<<< From Sun's Web Page. http://java.sun.com/docs/hotspot/PerformanceFAQ.html#15 >>>>>>>> Should I pool objects to help GC? Should I call System.gc() periodically? Should I warm up my loops first so that Hotspot will compile them? The answer to all of these is No! Pooling objects will cause them to live longer than necessary. The garbage collection methods will be much more efficient if you let it do the memory management. We strongly advise taking out object pools. Don't call System.gc(), HotSpot will make the determination of when its appropriate and will generally do a much better job. If you are having problems with the pause times for garbage collection or it taking too long, then see the pause time question above. Warming up loops for HotSpot is not necessary. HotSpot now contains On Stack Replacement technology which will compile a running (interpreted) method and replace it while it is still running in a loop. No need to waste your applications time warming up seemingly infinite (or very long running) loops in order to get better application performance. See also Tuning Garbage Collection with the 1.3.1 Java Virtual Machine. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
