Creating FIP takes time
Bug #1880969 reported by
Maciej Jozefczyk
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Low
|
Unassigned |
Bug Description
I noticed on upstream and downstream gates that while creating FloatingIP for action like:
neutron floatingip-create public
For ml2/ovs and ml2/ovn this operation takes minimum ~4 seconds.
The same we can find on u/s gates from rally jobs [1].
While we put the load on Neutron server it normally takes more than 10 seconds.
For ML/OVN creating a FIP doesn't end with creating NAT entry in OVN NBDB row. So its clearly only API operation.
Maybe we can consider profiling it?
summary: |
- Creating FloatingIP takes time + Creating FIP takes time |
description: | updated |
Changed in neutron: | |
importance: | Undecided → Low |
To post a comment you must log in.
I think this is the profiled output for the given job: /98a898dcf3dfb1 090155- da3b599be5166de 1dcb38898c60ea3 c9.ssl. cf5.rackcdn. com/729588/ 1/check/ neutron- rally-task/ dd55aa7/ results/ report. html#/NeutronNe tworks. associate_ and_dissociate_ floating_ ips/output
https:/
(wait a little till it is fully loaded)
There it is clearly visible wsgi things are the longest for creating floating ip, but I am not an expert on profiling so have no idea about the depths of this specific profiling for FIPs