BIND 10 #2839: add dtrace probe hooks into BIND 10 (in the performance critical path)
BIND 10 Development
do-not-reply at isc.org
Mon Mar 4 09:09:33 UTC 2013
#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 vorner):
I'm not against dtrace (and I didn't study about what the probes are). But
I'd like to point to the oprofile project, which uses the hardware support
in CPU. In case of AMD CPU, you can get very accurate results of what part
of code is the bottleneck (accurate to separate machine instructions) and
the reason to it (you can ask to measure run time of the instructions,
number of cache misses, number of waits for locks, etc). And all that
without performance impact.
Unfortunately, that is a linux-only tool.
--
Ticket URL: <http://bind10.isc.org/ticket/2839#comment:1>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list