Dan. I read the kcachegrind manual last night and early this morning and I
think we figured out how to visualize the tcmalloc source code hit counts
generated by callgrind. Thank you.
On Thu, Sep 15, 2011 at 7:08 PM, Dan Kegel <[email protected]> wrote:
> On Thu, Sep 15, 2011 at 6:35 PM, Frank Chang <[email protected]>
> wrote:
> > Hi, We recently built and linked in the google perftools libtcmalloc
> custom
> > memory allocator into a prototype software tool we are researching at a
> > basic research level. We found that on WIndows and Linux, the speed of
> this
> > research software tool sped by 350% when we linked in libtcmalloc. Now,
> we
> > are trying to analyze why this fortuitous speed improvement using
> > kcachegrind -- callgrind, How do find out which tcmalloc functions are
> > responsible for the speed improvement using the kcachegrind -- callgrind
> > profiler? Thank you.
>
> Before you go there, have you read
> http://goog-perftools.sourceforge.net/doc/tcmalloc.html ?
>
------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
