commit 840e04b6f122f022f67b600ed2f96ae5e92eabe0
Author: Kevin Benton <email address hidden>
Date: Wed Feb 15 20:49:45 2017 -0800
Skip native DHCP notifications on status change
On profiling the get_devices_details communications between
the agent and the server, a significant amount of time
(60% in my dev env) is being spent in the AFTER_UPDATE events
for the port updates resulting from the port status changes.
One of the major offenders is the native DHCP agent notifier.
On each port update it ends up retrieving the network for the
port, the DHCP agents for the network, and the segments.
This patch addresses this particular issue by adding logic to
skip a DHCP notification if the only thing that changed on the
port was the status. The DHCP agent doesn't do anything based on
the status field so there is no need to update it when this is
the only change.
Reviewed: https:/ /review. openstack. org/434677 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=840e04b6f12 2f022f67b600ed2 f96ae5e92eabe0
Committed: https:/
Submitter: Jenkins
Branch: master
commit 840e04b6f122f02 2f67b600ed2f96a e5e92eabe0
Author: Kevin Benton <email address hidden>
Date: Wed Feb 15 20:49:45 2017 -0800
Skip native DHCP notifications on status change
On profiling the get_devices_details communications between
the agent and the server, a significant amount of time
(60% in my dev env) is being spent in the AFTER_UPDATE events
for the port updates resulting from the port status changes.
One of the major offenders is the native DHCP agent notifier.
On each port update it ends up retrieving the network for the
port, the DHCP agents for the network, and the segments.
This patch addresses this particular issue by adding logic to
skip a DHCP notification if the only thing that changed on the
port was the status. The DHCP agent doesn't do anything based on
the status field so there is no need to update it when this is
the only change.
Change-Id: I948132924ec502 1a9db78cf17efbb a96b2500e8e
Partial-Bug: #1665215