Hi,
FWIW, I've been trying to understand op delays under very heavy write
load, and have been working a little with the policy throttler in hopes of
using throttling delays to help track down which ops were backing up.
Without much success, unfortunately.
When I saw the wip-osd-op-tracking branch, I wondered if any of this
stuff might be helpful. Here it is, just in case.
-- Jim
Jim Schutt (6):
msgr: print message sequence number and tid when receiving message
envelope
common/Throttle: track sleep/wake sequences in Throttle, report them
for policy throttler
common/Throttle: throttle in FIFO order
common/Throttle: FIFO throttler doesn't need to signal waiters when
max changes
common/Throttle: make get() report number of waiters on entry/exit
msg: log Message interactions with throttler
src/common/Throttle.h | 75 +++++++++++++++++++++++++++++++-------------
src/msg/Message.h | 71 +++++++++++++++++++++++++++++++++++------
src/msg/SimpleMessenger.cc | 22 +++++++++---
3 files changed, 129 insertions(+), 39 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
