openstack/openstack-manuals
Code Issues Proposed changes
4e666e2542
openstack-manuals/doc/admin-guide-cloud/source/blockstorage-api-throughput.rst
venkatamahesh e08ae456c0 [admin-guide] Fix rst mark-ups for block-storage files 
1.) Also deleted the commands that are explaining
for different linux distros.
2.) And also replaced one TODO link

Change-Id: I2557ff8bd93b21129b26a03c8c2b0b714949b9cf
2015-12-16 15:47:58 +05:30

1.4 KiB
Raw Blame History

Increase Block Storage API service throughput

By default, the Block Storage API service runs in one process. This limits the number of API requests that the Block Storage service can process at any given time. In a production environment, you should increase the Block Storage API throughput by allowing the Block Storage API service to run in as many processes as the machine capacity allows.

Note

The Block Storage API service is named openstack-cinder-api on the following distributions: CentOS, Fedora, openSUSE, Red Hat Enterprise Linux, and SUSE Linux Enterprise. In Ubuntu and Debian distributions, the Block Storage API service is named cinder-api.

To do so, use the Block Storage API service option osapi_volume_workers. This option allows you to specify the number of API service workers (or OS processes) to launch for the Block Storage API service.

To configure this option, open the /etc/cinder/cinder.conf configuration file and set the osapi_volume_workers configuration key to the number of CPU cores/threads on a machine.

On distributions that include openstack-config, you can configure this by running the following command instead:

# openstack-config --set /etc/cinder/cinder.conf \
  DEFAULT osapi_volume_workers CORES

Replace CORES with the number of CPU cores/threads on a machine.