BIND 10 #1565: document how to profile - gprof

[BIND 10 Development]

#1565: document how to profile - gprof
-------------------------------------+-------------------------------------
                   Reporter:  jelte  |                 Owner:  haikuo
                       Type:  task   |                Status:  accepted
                   Priority:  major  |             Milestone:
                  Component:         |  Sprint-20120207
  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      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:3 haikuo]:

 > I have a suggestion to handle the name conflict. we could modify the
 bind10 scripts in PATH/sbin, add "spawn_env[ 'GMON_OUT_PREFIX' ] =
 self.args[0]" to _spawn function, like that:
 >
 > [zhanghk at iscloud01 tmp]$ diff bind10 bind10-new
 > 144a145
 > >         spawn_env[ 'GMON_OUT_PREFIX' ] = self.args[0]
 >
 > then bind10 will produce different profiling files, and we can use gprof
 to collect data for the differenct ELF executable files .

 I personally would like to avoid hardcoding profiling specific
 environment variable name to the script source.  IMO any hardcode is
 generally evil and make the implementation less maintainable, and
 especially in this case this information is unnecessary in the vast
 majority of actual usage (running it in a production environment or in
 tests).

 I'd suggest considering a different approach, such as tweaking
 run_bind10.sh script where the additional env variable is defined.

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