Project

General

Profile

Actions
Copy link

Bug #47344

closed

osd: Poor client IO throughput/latency observed with dmclock scheduler during background recovery ops.

Added by Sridhar Seshasayee over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Sridhar Seshasayee
Category:
Performance/Resource Usage
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
37031
Crash signature (v1):
Crash signature (v2):

Description

Regardless of the higher weightage given to client IO when compared to
recovery IO, poor client throughput/latency is observed.

Analysis revealed that recovery IO delivered via MOSDPGPush/MOSDPGPushReply
messages are always pushed to the "immediate" queue regardless of the
priority. This resulted in the starvation of the scheduler queue containing
client Ops and therefore the poor performance observed on the client.

The fix involves properly categorizing recovery ops and pushing them into
the scheduler queue so that the QoS requirements are met.

Actions
Copy link
 #1

Updated by Sridhar Seshasayee over 3 years ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 37031
Actions
Copy link
 #2

Updated by Sridhar Seshasayee over 3 years ago

  • Subject changed from osd: Poor client IO throughput/latency observed with dmclock scheduler to osd: Poor client IO throughput/latency observed with dmclock scheduler during background recovery ops.
Actions
Copy link
 #3

Updated by Neha Ojha over 3 years ago

  • Status changed from Fix Under Review to Resolved
Actions
Copy link

Also available in: Atom PDF