BIND 10 #2871: Fake work for resolution
BIND 10 Development
do-not-reply at isc.org
Wed Apr 24 15:52:45 UTC 2013
#2871: Fake work for resolution
-------------------------------------+-------------------------------------
Reporter: vorner | Owner:
Type: task | pselkirk
Priority: medium | Status:
Component: resolver | reviewing
Keywords: | Milestone:
Sensitive: 0 | Sprint-20130423
Sub-Project: DNS | Resolution:
Estimated Difficulty: 4 | CVSS Scoring:
Total Hours: 0 | Defect Severity: N/A
| Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Changes (by vorner):
* owner: vorner => pselkirk
Comment:
Hello
Replying to [comment:8 pselkirk]:
> - Copyright date in 6 of the new files is 2009, and copyright in the
existing files has not been updated to 2013.
Hopefully updated. I copy-pasted the headers, which is obviously wrong
from time to time. I hope the lawyers wouldn't make us add the header
nobody reads anyway…
> - The last 3 commits on this branch have messages that start with
"[2738]", which seems unrelated to this ticket.
I created a new branch, where this should be fixed. Look at trac2871_2.
> - The existence of random factors (for cache hit, and especially for
upstream query completion time) makes this less of a rigid benchmark than
a statistical exercise. OTOH, over the course of 1000 iterations per run,
it smooths out pretty well - I found less than 0.5% standard deviation
over 12 runs.
Does this matter for the purpose? I mean, if there are enough samples
(generated queries, or whatever), it should just converge to be something
almost same every time. And we are looking for large differences in the
models anyway (we'll get more inaccurate by the fact we use the fake work
instead of real resolution, than from the averages).
But if you have concrete idea how to solve this problem without much work,
I'm not opposed.
--
Ticket URL: <http://bind10.isc.org/ticket/2871#comment:9>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list