Remove extraneous trace in linux/dhcp.py
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Invalid
|
Undecided
|
Unassigned | ||
Icehouse |
Fix Released
|
Undecided
|
Unassigned | ||
neutron |
Fix Released
|
Undecided
|
Billy Olsen | ||
Juno |
Fix Released
|
Undecided
|
Stephen Ma | ||
neutron (Ubuntu) |
Fix Released
|
Low
|
Billy Olsen | ||
Trusty |
Fix Released
|
Low
|
Unassigned |
Bug Description
[Impact]
The debug tracepoint in Dnsmasq.
The trace point is unnecessary since the data is being written to disk and the file can be examined in a worst case scenario. The added performance overhead is an order of magnitude in difference (~.5 seconds versus ~.05 seconds at 1500 ports).
[Test Case]
1. Deploy OpenStack using neutron for networking
2. Create 1500 ports
3. Observe the performance degradation for each port creation.
[Regression Potential]
Minimal. This code has been running in stable/juno, stable/kilo, and above for awhile.
[Other Questions]
This is likely to occur in OpenStack deployments which have large networks deployed. The degradation is gradual, but the performance becomes unacceptable with large enough networks.
Related branches
Changed in neutron: | |
assignee: | nobody → Billy Olsen (billy-olsen) |
status: | New → In Progress |
Changed in neutron: | |
milestone: | none → kilo-3 |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | kilo-3 → 2015.1.0 |
description: | updated |
Changed in neutron (Ubuntu): | |
assignee: | nobody → Billy Olsen (billy-olsen) |
Changed in cloud-archive: | |
status: | New → Confirmed |
Changed in neutron (Ubuntu): | |
importance: | Undecided → Low |
Changed in neutron (Ubuntu Trusty): | |
importance: | Undecided → Low |
Changed in cloud-archive: | |
status: | Confirmed → Invalid |
Fix proposed to branch: master /review. openstack. org/149784
Review: https:/