![]() The SM throttling is a feature that limits the number of parallel service-enabling processes at a time. The SM throttling mechanism is always ON, during and after startup. Whenever SM controlled services transition to enabled status, it takes part of the process. By default, the SM throttling allows a maximum of 2 parallel service enabling processes at a time, but the throttling size is configurable, by means of the field ENABLING_THROTTLE from the CONFIGURATION table in the SM-DB database. Hence, it is possible to disable the SM throttling by increasing the throttling size to a reasonable big enough value, such way to enable full capacity of parallel service enabling. This commit improves system performance by disabling the SM throttling for AIO-SX systems, while still keeping the SM throttling mechanism, should it ever be needed as a fallback, for robustness reasons. In order to evaluate the SM throttling feature, and its costs in terms of performance, the throttling size was modified such way to disable the feature, from value 2 to 1000, and a series of tests were conducted to evaluate stability and performance benefits. Test Plan: - Fresh Install and bootstrap (PASS) - Lock/Unlock (PASS) - Restart SM service (PASS) Story: 2010802 Task: 48312 Change-Id: Ie96115293049e9939bc43feb2ad11432dd318323 Signed-off-by: Matheus Guilhermino <matheus.machadoguilhermino@windriver.com> |
||
---|---|---|
api-ref/source | ||
devstack | ||
doc | ||
releasenotes | ||
service-mgmt | ||
service-mgmt-api | ||
service-mgmt-client | ||
service-mgmt-tools | ||
stx-ocf-scripts | ||
.gitignore | ||
.gitreview | ||
.zuul.yaml | ||
CONTRIBUTORS.wrs | ||
LICENSE | ||
README.rst | ||
bindep.txt | ||
centos_build_layer.cfg | ||
centos_dev_wheels.inc | ||
centos_iso_image.inc | ||
centos_pkg_dirs | ||
centos_stable_wheels.inc | ||
debian_build_layer.cfg | ||
debian_iso_image.inc | ||
debian_pkg_dirs | ||
github_sync.trigger | ||
pylint.rc | ||
test-requirements.txt | ||
tox.ini |
README.rst
ha
The starlingx/ha repository handles High Availability services1.
Its key component is the StarlingX Service Management (SM), which coordinates the StarlingX services.
This repository is not intended to be developed standalone, but rather as part of the StarlingX Source System, which is defined by the StarlingX manifest2.