Description of problem:
Neutron API response times between Mitaka and Newton has significantly increased.
Looking at Mitaka: http://10.12.23.141/goto/102518200d0e04774e4fe6ffec47961e
Looking at Newton: http://10.12.23.141:80/goto/883c5b0b082fa4c863bf00ed6a338046
Looking at upstream Rally scenarios, we do see a change in response times as well (pointed out by Ihar)
However Brent Eagles points out that OOO incorrectly deploys Neutron with API workers set to 0, which would default to 1.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install a with OOO
2. Run Browbeat with supplied config file : https://gist.github.com/jtaleric/eb8c090c2562c8842d8a8183b29ffc2f
Brent has a TripleO patch to change the default of api_workers from 0 (No workers) to the empty string, so that TripleO won't set a value at all and use Neutron's default, which is the number of CPUs. Meanwhile Joe is re-running the tests with api_workers set to ''.
Following up on the references to upstream Rally - some of the upstream Rally scenarios differ significantly in Rally settings, eg. ports_per_network in create_and_list_ports is set to 2 in mitaka (PS 363558) but to 100 in master (PS 364123) so the results need detailed inspection w.r.t. their settings.
That said, IMHO they are still worth inspection. E.g. in the case of create_and_list_networks ( - master,  - mitaka), the settings is almost the same, the only rally differences seem the number of iterations (100 in master, 40 in mitaka), in network quota (100 in master, -1 in mitaka), and in sla (but that is rather irrelevant for the results). The results however show rather a significant difference in the times.
Tested in openstack-tripleo-heat-templates-5.2.0-3.el7ost.noarch
The amount of workers configured according to CPU amount of the controller, in my setup 4.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.