search for: tmp06

Olly Betts <olly at survex.com> wrote: > The report you show seems to be just the time take by each function > directly rather than including functions it calls. It looks like a lot > of the time is spent in cursor movement, as totalling up things that > seem like they'd be due to that I quickly get to 40+% but it's hard > to tell if that's about the actual total

...akes for a confusing error message. The docs say to link with -lprofiler but it seems to work fine to LD_PRELOAD it and I find that easier to work with so I use it like so: LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libprofiler.so CPUPROFILE=$HOME/prof.out /usr/bin/xapian-compact /mnt/data/scratch/text/tmp06.db /mnt/data/scratch/text/06.db google-pprof /usr/bin/xapian-compact $HOME/prof.out At the prompt inside, "gv" renders a callgraph in postscript and "callgrind" generates a file like that from valgrind's callgrind tool which you can inspect with kcachegrind, etc. Cheers,...

...r message. > > The docs say to link with -lprofiler but it seems to work fine to > LD_PRELOAD it and I find that easier to work with so I use it like so: > > LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libprofiler.so CPUPROFILE=$HOME/prof.out /usr/bin/xapian-compact /mnt/data/scratch/text/tmp06.db /mnt/data/scratch/text/06.db Ah, thanks, I managed to get that part working and generated a prof.out file, at least > google-pprof /usr/bin/xapian-compact $HOME/prof.out > > At the prompt inside, "gv" renders a callgraph in postscript and > "callgrind" generate...