BIND 10 #1565: document how to profile - gprof
BIND 10 Development
do-not-reply at isc.org
Fri Feb 3 01:35:09 UTC 2012
#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 haikuo):
Definitely jinmei is right,hardcoding only for profiling feature would
cause difficulty to maintenance. But from my point of view, tweaking
run_bind10.sh script is not a perfect approach, because it is hard for our
bind10 user to modify bind10 code. If we are the only users for profiling
feature, Jinmei's approach is OK.
If we launch the "run_bind10.sh" scripts, we have to maintain one more
file, it may be hard for us.
Could we add an option for bind10 script(PREFIX/sbin/bind10)? like "--
profiling" or something. then bind10 could open the switch to assign the
environment variable.
--
Ticket URL: <http://bind10.isc.org/ticket/1565#comment:5>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list