On Wed, Feb 01, 2006 at 01:52:02PM +0200, Marko Asplund wrote: > On 2006-02-01, at 00.45, Tim Bunce wrote: > > >There are memory allocation debugging tools that may help to isolate > >the original problem and so give some confidence that it's not present > >in the other configurations. > > I'am not really familiar with such tools, can you recommend a good > tool for this? How about Valgrind?
Try http://www.google.com/search?q=malloc+debug+tools > >>I've reported this issue to Oracle but does anyone have clues on what > >>is causing this or suggestions on how to get this fixed on the Perl > >>side? I'd really need to use -Dusemymalloc and Oracle Instant Client. > > > >Why? > > I don't have empirical data on this but several sources (among others > Perl distribution INSTALL file, mod_perl Cookbook) hint that - > Dusemymalloc may give better performance and use less memory. That doesn't sound like a good enough reason. More like premature optimization. I'd only return to this option once you've proven you have performance problems and you've then exhausted all higher-level optimizations. Tim.
