The current interval between ProcessLauncher checks of whether
a child process has exited - 0.01s - prioritizes fast respawning of
children at the expense of cpu usage. This tradeoff may not be
appropriate for all clients of the class, so this patch makes the
interval configurable. The current interval remains the default
to avoid changing expected behavior.
This patch was motivated by unnecessary idle cpu usage of the
Neutron service when configured to use ProcessLauncher-managed
worker processes.
Reviewed: https:/ /review. openstack. org/63017 /git.openstack. org/cgit/ openstack/ oslo-incubator/ commit/ ?id=32cd4c002d3 e1074c35032d103 66f3a968f8c46f
Committed: https:/
Submitter: Jenkins
Branch: master
commit 32cd4c002d3e107 4c35032d10366f3 a968f8c46f
Author: Maru Newby <email address hidden>
Date: Wed Dec 18 23:07:52 2013 +0000
Allow configurable ProcessLauncher liveness check
The current interval between ProcessLauncher checks of whether
a child process has exited - 0.01s - prioritizes fast respawning of
children at the expense of cpu usage. This tradeoff may not be
appropriate for all clients of the class, so this patch makes the
interval configurable. The current interval remains the default
to avoid changing expected behavior.
This patch was motivated by unnecessary idle cpu usage of the -managed
Neutron service when configured to use ProcessLauncher
worker processes.
Partial-Bug: #1095346
Change-Id: I2f5e06f98be1f7 5c21e6681967b57 3f5d88a4ed6