Most daemons have a "go as fast as you can then sleep for 30 seconds"
strategy towards resource utilization; the object-updater and
object-auditor however have some "X_per_second" options that allow
operators much better control over how they spend their I/O budget.
This change extends that pattern into the account-replicator,
container-replicator, and container-sharder which have been known to peg
CPUs when they're not IO limited.
Reviewed: https:/ /review. openstack. org/614018 /git.openstack. org/cgit/ openstack/ swift/commit/ ?id=06cf5d298fb 6b103899aa358e1 cb4b828f502dc5
Committed: https:/
Submitter: Zuul
Branch: master
commit 06cf5d298fb6b10 3899aa358e1cb4b 828f502dc5
Author: Clay Gerrard <email address hidden>
Date: Mon Oct 29 14:49:48 2018 -0500
Add databases_ per_second to db daemons
Most daemons have a "go as fast as you can then sleep for 30 seconds"
strategy towards resource utilization; the object-updater and
object-auditor however have some "X_per_second" options that allow
operators much better control over how they spend their I/O budget.
This change extends that pattern into the account-replicator, replicator, and container-sharder which have been known to peg
container-
CPUs when they're not IO limited.
Partial-Bug: #1784753 384a1a6ab500b65 7c624426384
Change-Id: Ib7f2497794fa2f