Barry Lind <blind@xythos.com> wrote:
> Teofilis Martisius wrote:
> > On Mon, Oct 21, 2002 at 07:38:07PM -0700, Barry Lind wrote:
> >
> > Hmm, I know how all this works. I read JDBC driver code. However, I did
> > not find much better solution. First, when transfering data from stream,
> > the only logical solution is to put int into byte[]. And as far as I
> > understand byte[] arrays are already pooled. I doubt it is
> > posible/better to read other things than byte[] from the stream.
> >
>
> byte[] objects are not pooled. As for the rest of your email I will
> think about the options you have laid out and respond in more detail
later.
IIRC, the jvm at least in the newest versions does object pooling itself for
some classes. Maybe for byte[] two. There are some documents on the Sun Java
homepage that discourage from using object pools for anything that is not
related to external resources (like a database connection). They say the
internal algorithms are more efficient and object pooling can disturb the
generational garbage collection.
I am not sure about this. In older books I always read about pooling
everything, but nowadays there seem to be many opinions against it. At least
with modern JVMs. Anyone who has deeper knowledge of the topic or some
significant experience?
Best Regards,
Michael Paesold