BIND 10 #1263: Finish current experimental DHCP benchmarking work

[BIND 10 Development]

#1263: Finish current experimental DHCP benchmarking work
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  johnd
  stephen                            |                Status:  accepted
                       Type:  task   |             Milestone:  Sprint-
                   Priority:  major  |  DHCP-20111026
                  Component:  dhcp   |            Resolution:
                   Keywords:         |             Sensitive:  0
            Defect Severity:  N/A    |           Sub-Project:  DHCP
Feature Depending on Ticket:         |  Estimated Difficulty:  0
        Add Hours to Ticket:  0      |           Total Hours:  0
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by johnd):

 These look like useful options.

 Testing how long it takes for some operations could be handled by using
 both -r and -n, with a -d value large enough that the tool will wait a
 long time for any backlog that results to clear.  The statistics would
 then tell how long it took for the backlog to clear.

 What pass criteria would be be useful to set up, to allow for an
 unambiguous pass result?

 I did have a torture-like option in mind for the future.

 I'm thinking, for the initial version, from these suggestions adding:
 - The drop-threshold-abort
 - A version option
 - Include in the output the version and the parameters used
 - Explicit description of what the exit status means.  Perhaps just status
 1 if any dropped packets, unless other pass criteria options are added.
 - A test-period option, which seems to me an alternative to -n.

 Should any of the other suggested options be in the initial version?

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