BIND 10 #1564: document how to profile - valgrind/callgrind/kcachegrind

[BIND 10 Development]

#1564: document how to profile - valgrind/callgrind/kcachegrind
-------------------------------------+-------------------------------------
                   Reporter:  jelte  |                 Owner:  vorner
                       Type:  task   |                Status:  reviewing
                   Priority:  major  |             Milestone:
                  Component:         |  Sprint-20120124
  Unclassified                       |            Resolution:
                   Keywords:         |             Sensitive:  0
            Defect Severity:  N/A    |           Sub-Project:  DNS
Feature Depending on Ticket:         |  Estimated Difficulty:  0
        Add Hours to Ticket:  0      |           Total Hours:  0
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by jelte):

 * owner:  jelte => vorner


Comment:

 Replying to [comment:4 vorner]:
 > Hello
 >
 > I guess the setup_intree_bind10.sh is mostly for the B10_FROM_SOURCE
 variables (we really should be OK with just one to signal the whole in-
 source situation at once).
 >

 that is the goal, but right now it is easiest to just source this script
 (currently there are 3 vars needed i think, SOURCE, BUILD and
 MSGQ_SOCKET), though it also sets paths, making you have to type less :)

 > For building, maybe mentioning that a optimised build might be
 necessary?
 >
 > Does the thing count time or instructions?
 >

 instructions

 > Wouldn't running the thing be easier by:
 >
 > {{{
 > libtool --mode=execute valgrind --tool=callgrind ./src/bin/auth/b10-auth
 > }}}
 >
 > One doesn't have to guess what is the exact binary in the .libs
 directory, as it differs between OSes. Also, it would work even when the
 B10_FROM_SOURCE & friends are set by hand, without the whole set of
 library environment variables.
 >

 yes, but also more typing :) added.

 > Would you know of a tool other than kcachegrind? Than one has an
 unfortunate set of (mostly indirect) dependencies. I discovered only the
 commandline cachegrind_annotate.

 those two are the only ones I know of too. Added a section on annotate as
 well, but kcachegrind is the most informative one.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1564#comment:5>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development