Difference between revisions of "MultiAPIWorkersForNeutron"
(Created page with " == Summary == Support for multiple api processes for neutron. Blueprint: https://blueprints.launchpad.net/neutron/+spec/multi-workers-for-api-server == Rationale == Curre...") |
|||
| Line 14: | Line 14: | ||
All the changes neccessary for multi workers is done through introducing the related multi process codes from nova. And a new option 'api_workers' will be added to the config file to control the processes for neutron-server to be spawned. | All the changes neccessary for multi workers is done through introducing the related multi process codes from nova. And a new option 'api_workers' will be added to the config file to control the processes for neutron-server to be spawned. | ||
| + | |||
| + | == Configuration variables == | ||
| + | |||
| + | '''api_workers:''' Number of workers for Neutron API service. | ||
Latest revision as of 07:08, 15 August 2013
Summary
Support for multiple api processes for neutron.
Blueprint: https://blueprints.launchpad.net/neutron/+spec/multi-workers-for-api-server
Rationale
Currently, there is only one process running to handle different requests, that means all green threads are actually being scheduled within one system process, which results in only one processor core can be utilized. As API requests concurrency increase, the throughout doesn't increase because requests pipe-up and the response time of each request increase quickly. Similiar implementation has been added to Nova and others core projects of openstack.
Implementation
All the changes neccessary for multi workers is done through introducing the related multi process codes from nova. And a new option 'api_workers' will be added to the config file to control the processes for neutron-server to be spawned.
Configuration variables
api_workers: Number of workers for Neutron API service.
