> > Does anyone know of a good way to solve this problem? Any suggestions
> > around the issue of object creation performance are welcome.
>
> One way to handle this problem would be to create an Object pool.
> There was an article on javaworld (www.javaworld.com) a few months
> back. Basically
I do believe the synchronization improvements are already shipping with JDK1.2beta4,
which is available for Solaris and Win32. At any rate, synchronization suddenly got
an order of magnitude faster from v1.1.6 to v1.2beta4.
-dan
[EMAIL PROTECTED]
Paul Reavis wrote:
> Steve Byrne wrote:
> >
> >
Steve Byrne wrote:
>
> Uncle George writes:
> > interesting, considering that 1.2 isn't out yet. U got a mole in the sun
> > organization?
>
> I used to work there until December of 97. I kept ensuring that 1.2 compiling
> cleanly with gcc, so the port to Linux wouldn't be too bad. Being on
Uncle George writes:
> interesting, considering that 1.2 isn't out yet. U got a mole in the sun
> organization?
I used to work there until December of 97. I kept ensuring that 1.2 compiling
cleanly with gcc, so the port to Linux wouldn't be too bad. Being on the
inside, you get presentations
Steve Byrne wrote:
>
> Vincent Trussart writes:
> > One way to handle this problem would be to create an Object pool.
> > There was an article on javaworld (www.javaworld.com) a few months
> > back. Basically, instead of creating new objects you request them from the
> > pool. When they are
interesting, considering that 1.2 isn't out yet. U got a mole in the sun
organization?
gat
just ;)
Steve Byrne wrote:
> Right. I've known projects that have done this and won big. Creating objects
> is somewhat expensive because it's a synchronous operation, and synchronized
> operations are s
Vincent Trussart writes:
> "B. Craig Taverner" wrote:
>
> > Hi,
> >
> > I'm dealing with a performance issue in java where it appears that
> > performance is noticably affected by the fact that many (thousands) of
> > relatively small objects need to be created very quickly (multiple small
Craig,
Like C/C++, Java uses strong type constraints to prevent
programmers from accessing data in an inconsistent way
(e.g. casting objects). Unlike C/C++, Java prevents you
from having direct access to program memory. In C/C++,
it is common to use a pointer to locate a variable in memory
a
On Mon, 28 Sep 1998 21:34:24 +0200 (CEST), B. Craig Taverner wrote:
>I'm dealing with a performance issue in java where it appears that
>performance is noticably affected by the fact that many (thousands) of
>relatively small objects need to be created very quickly (multiple small
>memory allocat
"B. Craig Taverner" wrote:
> Hi,
>
> I'm dealing with a performance issue in java where it appears that
> performance is noticably affected by the fact that many (thousands) of
> relatively small objects need to be created very quickly (multiple small
> memory allocations). From my C/C++ backgrou
Hi,
I'm dealing with a performance issue in java where it appears that
performance is noticably affected by the fact that many (thousands) of
relatively small objects need to be created very quickly (multiple small
memory allocations). From my C/C++ background I would have considered
solving this
11 matches
Mail list logo
