Opened 14 months ago

Last modified 3 weeks ago

#5115 new defect

perfdhcp command options unnecessarily restrictive

Reported by: raybellis Owned by:
Priority: medium Milestone: Kea1.4
Component: perfdhcp Version: git
Keywords: perfdhcp Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: Low
Sub-Project: DHCP Feature Depending on Ticket: perflab integration
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


The -D<max-drop>, -n<num-request>, -p<test-period> and -t<report> options to perfdhcp all require use of the -r<rate> option.

I can't see any good reason for this restriction, nor any actual interdependency within the code.


Attachments (1)

perfdhcp.diff (2.2 KB) - added by raybellis 14 months ago.

Download all attachments as: .zip

Change History (5)

Changed 14 months ago by raybellis

comment:1 Changed 14 months ago by tomek

  • Milestone changed from Kea-proposed to Kea1.2
  • Priority changed from medium to low

As discussed on 2016-01-26 call, moving to 1.2 low.

comment:2 Changed 12 months ago by tomek

  • Milestone changed from Kea1.2 to Kea1.2-final

Code freeze for 1.2-beta. Moving all remaining open tickets to 1.2-final.

comment:3 Changed 11 months ago by tomek

  • Milestone changed from Kea1.2-final to Outstanding Tasks

As discussed on 2017-04-13 call, moving to outstanding.

comment:4 Changed 3 weeks ago by tomek

  • Milestone changed from Outstanding Tasks to Kea1.4
  • Priority changed from low to medium

Given the recent sudden interest in performance measurements, moving this ticket to 1.4 as medium. The patch is there, so review should be quick.

Note: See TracTickets for help on using tickets.