🚀 go-pugleaf

Elias:

Invest in a profiler or similar tool (like OptimizeIt or JProbe). 
Without such a tool, tuning is a deep, dark black hole that will suck
out the will to live from the development team and bleed you dry in
terms of dollars spent v. gains made.  These tools will let you see
where the choke points are and, more importantly, let you make an
educated decision about where to focus resources.  Nothing worse then
spending two weeks on a "performance" problem to see that all those
milliseconds saved really results in a 2 second actual benefit!

-Rich

Elias A. Fayyad wrote:
> 
> Greetings,
> 
> Does anyone out there have pointers to books or information to
> tuning the performance of a Java (specifically JBuilder)
> application?  We're experiencing some performance problems, and
> we've looked at the logical things (un-necessary object
> instantiations, etc.), but if anyone can point to some written
> resources, that would be much appreciated.
> 
> Thanks,
> Elias.
> _______________________________________________________________________
> 
>  Elias A. Fayyad
>  Alta Analytics, Inc., 929 Eastwind Drive, Suite 203
>  Westerville, OH 43081

-- 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rich Wilkman
Senior Quality Assurance Engineer
Borland JBuilder Team

If you see something that looks like an opinion up there,
it's mine and mine alone.

Mail sent to me from the newsgroups won't bounce but will
be ignored.  If I have time, I'll respond, but you  have
a better chance if you confine your posts to the newsgroups
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=