BIND 10 #2606: DHCP Performance Testing and Enhancement
BIND 10 Development
do-not-reply at isc.org
Thu Feb 14 16:50:49 UTC 2013
#2606: DHCP Performance Testing and Enhancement
-------------------------------------+-------------------------------------
Reporter: stephen | Owner:
Type: task | marcin
Priority: medium | Status:
Component: dhcp | reviewing
Keywords: | Milestone:
Sensitive: 0 | Sprint-DHCP-20130214
Sub-Project: DHCP | Resolution:
Estimated Difficulty: 0 | CVSS Scoring:
Total Hours: 0 | Defect Severity: N/A
| Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Changes (by tmark):
* owner: tmark => marcin
Comment:
Overall, very well done given the rather informal requirements.
A few questions:
1. Should there by any prerequisite statements to determine what if any
other load
exists on either machine and/or network? Would it be helpful to have
gathered some
basic network metrics, ping time etc?
2. Should Test Procedure include statements indicating a required level of
isolation
or to ensure that there is no other traffic against the bind10 or its
components.
For example, on the DHCP test lab, the windows boxes apparently are
always trolling
DHCP4 through out the lab. This introduces spurious traffic.
Pertaining to the output collected. It would be perhaps, helpful to have
the
charts together on a single sheet, maybe stacked vertically. Also the
legend does
not specify units of measure for time.
Minor comment on dhcp-val/doc/performance-test-setup.txt:
In the paragraph, near the end of document:
" The server system should already have all prerequsities needed to
build BIND10 installed.
In case any of them is missing for any reason, please refer to BIND10
System Specific Notes
for the BIND10 setup on the FreeBSD:
http://bind10.isc.org/wiki/SystemNotesFreeBSD"
I believe you should replace "server" with "client" or "perf-s1.lab".
An observation:
It is interesting that regardless of the backend employed and the ex rate,
the average delay
time is essentially the same until you hit a level that overwhelms the
system and the drop rate
gets large. In other words, the minimum response time doesn't really
change until you break the
system.
--
Ticket URL: <http://bind10.isc.org/ticket/2606#comment:5>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list