BIND 10 #1951: Familiarize with perfdhcp implemented functionality

[BIND 10 Development]

#1951: Familiarize with perfdhcp implemented functionality
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  marcin
  stephen                            |                Status:  reviewing
                       Type:  task   |             Milestone:  Sprint-
                   Priority:         |  DHCP-20120514
  medium                             |            Resolution:
                  Component:         |             Sensitive:  0
  perfdhcp                           |           Sub-Project:  DHCP
                   Keywords:         |  Estimated Difficulty:  8
            Defect Severity:  N/A    |           Total Hours:  9.5
Feature Depending on Ticket:         |
        Add Hours to Ticket:  .5     |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by stephen):

 * hours:  9 => .5
 * owner:  stephen => marcin
 * totalhours:  0 => 9.5


Comment:

 Comments in http://bind10.isc.org/wiki/DhcpBenchmarking are very useful,
 thank-you.  (I made some minor corrections to it, just correcting some
 typos and rephrasing some sentences - no technical changes.)  This ticket
 can now be closed.

 A few comments on the issues you raise:

 * We certainly need two containers, one ordered by send time to detect
 when a reply is lost, and one random access container to locate the packet
 by xid.  I think you are right, combining the two in a multi-index
 container is likely to be the easiest to implement.  (Just as an aside,
 caching the next sent packet when a received packet is located is a nice
 touch; if we can keep it without too many problems, we should.)
 * I would suggest that we do use the BIND 10 logging, even if it does add
 additional dependencies on the BIND 10 library.  It forces a discipline on
 documenting messages and will server to tie it in with BIND 10.  If it
 proves cumbersome, it will be relatively easy to write a replacement
 light-weight logger using the same interface.

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