BIND 10 #2605: DHCP Testing: Performance Tool

BIND 10 Development do-not-reply at isc.org
Fri Mar 29 09:49:44 UTC 2013


#2605: DHCP Testing: Performance Tool
-------------------------------------+-------------------------------------
            Reporter:  stephen       |                        Owner:  tmark
                Type:  task          |                       Status:
            Priority:  medium        |  reviewing
           Component:  dhcp          |                    Milestone:
            Keywords:                |  Sprint-DHCP-20130411
           Sensitive:  0             |                   Resolution:
         Sub-Project:  DHCP          |                 CVSS Scoring:
Estimated Difficulty:  0             |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by marcin):

 * owner:  marcin => tmark


Comment:

 Replying to [comment:6 tmark]:
 > > (Pass Criteria):
 > > Checking perfdhcp output is ok. Once perfdhcp generates 4 or 2-way
 exchanges for the number of clients it simulates the client id IS EXPECTED
 to be reset and the next exchanges are initiated by the clients for which
 leases should exist in the data base. In other words, if you simulate 100
 clients and you setup perfdhcp to finish after 105 requests you should
 have 100 leases in the lease database. Right now, the test simulates 105
 clients and does exactly 105 requests so the client reset is not verfied.
 > >
 >
 > Actually both of the 105 client tests already have a step under pass
 criteria
 > to verify the number of leases. You just didn't look hard enough.

 Yes. I saw there is a step to verify that 105 leases has been added to the
 database. But, I was rather referring to the fact that you simulate 105
 clients and run 105 exchanges which results in 105 unique leases. My
 suggestion was to simulate 100 clients and trigger 105 requests and expect
 to have 100 unique leases. Similar scenario is covered by v4.four_packet
 test but it simulates 1 client requesting lease five times. This is sort
 of special case when you simulate only one client so I thought it could be
 extended in the v4.plus_100_clients test.

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


More information about the bind10-tickets mailing list