Oliver Jowett wrote:
> I can only speculate, since the java profiling tools are so bad -- I'm
> yet to get a good CPU profile out of this bit of code. It all *seems*
> fairly cheap so I can only guess that it's an accumulation of many
> small operations along the way. Object creation doesn't seem to be
> the root of the problem, as even with heap settings that avoid GCing
> frequently it's chewing CPU the whole time, not just during GCs.
>
> I should really do some more profiling of this area, I've just been
> avoiding it because it's so painful to do..
Fair enough. When I finish this patch, I'll certainly do some comparative
testing and look forward to your own experiences. Finishing is starting to
look not *so* far away any longer -- I just need to get batch updates and
updatable result sets working, do the prepared statement and cursor stuff for
v3 extended query, and then test and clean up.
--
www.designacourse.com
The Easiest Way to Train Anyone... Anywhere.
Chris Smith - Lead Software Developer/Technical Trainer
MindIQ Corporation
