neutron-server initiation is time-consuming with a large vxlan/gre range
Bug #1324875 reported by
Xurong Yang
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Low
|
Unassigned |
Bug Description
When we configure VXLAN range [1,16M], neutron-server service costs long time and cpu rate is very high(100%) when initiation. One test base on postgresql has been verified: more than 1h when VXLAN range is [1, 1M].
Changed in neutron: | |
assignee: | nobody → Xurong Yang (idopra) |
tags: | added: ml2 |
Changed in neutron: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in neutron: | |
milestone: | none → juno-2 |
Changed in neutron: | |
milestone: | juno-2 → juno-3 |
Changed in neutron: | |
milestone: | juno-3 → juno-rc1 |
Changed in neutron: | |
status: | In Progress → Fix Committed |
assignee: | Cedric Brandily (cbrandily) → nobody |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | juno-rc1 → 2014.2 |
To post a comment you must log in.
How about this algorithm?
first we populate a small block of resources into db, and then have a background thread monitoring the allocation status. If the allocation meets a criteria, the thread will populate one more block of resources into db.
take the vxlan ranges: 1..100000, we divide it into 100 blocks of 1000, first one 1000 is populated into db, and then another 1000 if needed.