[ft-devel] profiling (Re: Freetype-devel Digest, Vol 150, Issue 26)

[Hin-Tak Leung]

> Date: Fri, 28 Jul 2017 16:13:28 +0800
> From: Ewald Hew <address@hidden>
> To: Werner LEMBERG <address@hidden>
> Cc: address@hidden
> Subject: Re: [ft-devel] [GSoC] CID font
> support, and others

> > A starting point might be running
> ftbench with a profiler.  I
> > sometimes use valgrind for that:
> >
> >   valgrind --tool=callgrind
> ...
> >
> > The resulting data can then be
> >visualized with `kcachegrind'.  There
> > are certainly other profiling
> tools that you might find helpful.
 
Besides Werner's advice on valgrind/kcachegrind , I found GNU gprof useful 
enough at times . First you compile your code with the additional compiler 
switch "-pg" . After running your binary, it will leave behind an additional 
file called "[yourbinaryname].gprof" in the current directory which contains 
runtime statistics of your binary in the last execution. You then generate 
textual output summaries with gprof against that file. It is a lot lighter in 
weight than Valgrind, and with can tell you which lines are executed most 
often/with most culmulative time if used correctly.

Hin-Tak