> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Rickard Öberg
> So, if this is actually true, then there would be no point in doing
> pooling of stateless session beans either. Just instantiate as needed,
> and don't bother with it. I have no problem seeing why this could be
> true, but I haven't done any extensive testing of this.
There are two separate issues here:
1) cost of creating and garbage collecting
2) resource management
Granted, recent JVM's tend to make point 1) a little more irrelevant every day.
However, it is important in complex software such as application servers to be as
much as possible in control of resources, such as memory. Keeping a pool of
objects allows you to maintain a bound memory usage. JVM's may be fast at
allocating and GC'ing, these operations will still introduce spikes in the
resource consumption graph, and that might become a problem on the longer run.
--
Cedric
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
