diff options
author | Brian Foster <bfoster@redhat.com> | 2012-10-22 19:19:50 -0400 |
---|---|---|
committer | Vijay Bellur <vbellur@redhat.com> | 2012-12-17 02:13:32 -0500 |
commit | dd40167771daa5436d016ec4084d4ae0de62b00a (patch) | |
tree | 680fb2ec2898672be82b52ff6cb255b6c95fe076 /xlators/cluster/afr/src/afr-transaction.h | |
parent | e2b15d14e550e99653c1bb3abd072fc487fd0497 (diff) |
perf/io-threads: least-rate-limit least priority throttling
The 'least-rate-limit' io-threads translator option enables
throttling of least priority operations. This is initially intended
as a debug/diagnostic tool for users who might experience
overloaded servers via background activity (i.e., self-heal).
least-rate-limit defines the maximum number of least priority
operations the io-threads translator will dequeue in one second.
If the specified rate limit is met, the worker threads sleep for
the minimal amount of time before the next least priority operation
becomes available (or until a new request arrives).
The requests/second metric is generic and relative to a variety of
factors involved with a background operation (server, storage,
etc.). The most recent measured rate ("cached least rate") is added
to the io-threads state dump content (kill -USR1) to serve as a
reference point to throttle background activity under particular
conditions.
[This backport drops the iot_priv_dump() bits as they do not exist
in downstream.]
BUG: 853680
Change-Id: If7d28439372a2ea1a64e92e4a4b13826840a5248
Signed-off-by: Brian Foster <bfoster@redhat.com>
Reviewed-on: https://code.engineering.redhat.com/gerrit/1909
Reviewed-by: Vijay Bellur <vbellur@redhat.com>
Tested-by: Vijay Bellur <vbellur@redhat.com>
Diffstat (limited to 'xlators/cluster/afr/src/afr-transaction.h')
0 files changed, 0 insertions, 0 deletions