[NEUTRON-196] Updates use too many transactions Created: 27/Aug/18 Updated: 27/Aug/18 |
|
| Status: | Open |
| Project: | neutron |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Stephen Kitt | Assignee: | Josh Hershberg |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
We notices that the transaction rate limiter gets involved a lot during Neutron operations; digging a bit further shows that Neutron uses a lot of small transactions, which could be optimised (e.g. updates could use a read-write transaction instead of a read transaction to check existence, then write transaction to update). |