aea3edc229
Due to the limit of Python interpreter, API service of Manila can't really utilize underlying multi-core architecture even libraries like eventlet has been used. To make API service much more scalable, we'd adopt multi-process (worker) mode that has been used for long in Glance/Swift/Nova/Cinder. The default behavior isn't changed with this patch, Manila API service will still run in one process (default value of osapi_volume_workers is None). Implementation wise, a good portion of manila/service.py has been removed because those content has been merged in Oslo version of service module. manila/wsgi.py is also updated to adopt the change for multiple WSGI servers running in separate processes. DocImpact: 'New config option osapi_share_workers is used to specify number of API service workers (OS processes) to launch for Manila API service. Setting this config option to a proper value (e.g. osapi_share_workers = # of CPU cores/threads of the machine) can greatly improve the total throughput of API service [# of API requests can be handled per second].' Also removed out-dated comments in manila/cmd/api.py due to the fact that this bug [1] has been fixed in eventlet 0.9.13 This commit is port from two Cinder changes - [2] and [3]. [1] https://bitbucket.org/eventlet/eventlet/issue/92/eventletgreen-override-of-oswaitpid [2] I8361d0dc0d43040e48634ff1aee1324e5e0af466 [3] Iab32a3fe230a11692a8cad274304214247d6c2c6 Implement bp: multi-process-api-service Change-Id: I1cb98c938fd4e1dabe75c78a7ef392d6d7387dab |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| all.py | ||
| api.py | ||
| manage.py | ||
| scheduler.py | ||
| share.py | ||