BIND 10 #2839: add dtrace probe hooks into BIND 10 (in the performance critical path)

[BIND 10 Development]

#2839: add dtrace probe hooks into BIND 10 (in the performance critical path)
-------------------------------------+-------------------------------------
            Reporter:  cas           |                        Owner:
                Type:  enhancement   |                       Status:  new
            Priority:  medium        |                    Milestone:  New
           Component:  Unclassified  |  Tasks
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  Core          |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by cas):

 I found
 "An Overview of Software Performance Analysis Tools and Techniques: From
 GProf to DTrace"
 http://www.cse.wustl.edu/~jain/cse567-06/ftp/sw_monitors1/index.html

 and from the author of oprofile:
 (http://slashdot.org/comments.pl?sid=113922&cid=9651408)
 ----

 ''I wrote OProfile, and I currently use DTrace daily, and I can assure you
 that you are wrong when you claim they do the same thing."

 ''OProfile is useful for measuring system-wide resource consumers (for
 example, you can see what pieces of code are causing cache misses in the
 kernel when your apache process is in the kernel etc, or which user
 processes take up the most CPU time).''

 ''DTrace can also do something similar (though it needs a little more work
 yet). But DTrace does a LOT more than this. Imagine a system-wide (kernel,
 binaries, libraries) 'strace', where you can trivially choose what to
 print out, and what parts to strace, and under what circumstances. DTrace
 does even more than that.''

 ''OProfile can't tell you exactly why your system call is returning
 EINVAL. OProfile can't tell you why your application is causing cross-
 calls. OProfile can't tell you what processes are writing to what files,
 in real time. OProfile can't debug race conditions.''

 ''OProfile is a profiler: it does its job and nothing more. DTrace is,
 essentially, an instrumentation suite; one of its abilities is to function
 as a simple profiler.''

 ''You won't really get a notion of why DTrace is so useful until you try
 it''

 ----

 Both tools have their use cases, but they are different.

 About Dtrace probes:
 Adding DTrace probes to your applications
 http://www.ibm.com/developerworks/aix/library/au-dtraceprobes.html

 Putting developer-defined DTrace probe points in an application
 https://blogs.oracle.com/barts/entry/putting_user_defined_dtrace_probe

 Oracle DTrace Wiki
 https://wikis.oracle.com/display/DTrace/Introduction

 Userland DTrace support on FreeBSD
 https://wiki.freebsd.org/DTrace/userland

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