BIND 10 #2699: DHCP performance: use composite search indexes on the lease4 table to improve performance

BIND 10 Development do-not-reply at isc.org
Tue Feb 12 12:16:20 UTC 2013


#2699: DHCP performance: use composite search indexes on the lease4 table to
improve performance
-------------------------------------+-------------------------------------
            Reporter:  marcin        |                        Owner:  tmark
                Type:  defect        |                       Status:
            Priority:  high          |  reviewing
           Component:  dhcp4         |                    Milestone:
            Keywords:                |  Sprint-DHCP-20130214
           Sensitive:  0             |                   Resolution:
         Sub-Project:  DHCP          |                 CVSS Scoring:
Estimated Difficulty:  0             |              Defect Severity:
         Total Hours:  0             |  Medium
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by marcin):

 * owner:  marcin => tmark


Comment:

 I reviewed commit 20ad24c67485244b8e41823dca650ac5607eb778.

 I run some limited performance testing on this version and it seems to
 work as expected.

 In the '''MySQL script''' please update the date in the copyright header
 to 2012-2013.

 Your commit description on the trac2699 branch should be prefixed with
 [2699]. See http://bind10.isc.org/wiki/GitGuidelines for Git guidelines.

 I posted the question to the BIND10 chatroom on this. It seems that the
 common practice is to create another branch named trac2699_2 where the
 commit description can be corrected. The commit on the branch should be
 prefixed with [2699] (NOT [2699_2]!) and this branch will be later merged
 to master. You can use amend commit option to fix the comment.

 IMO, this change should have a corresponding !ChangeLog entry. Can you
 propose one?

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


More information about the bind10-tickets mailing list