Actions
Bug #58607
closedosd: PushOp and PullOp costs for mClock don't reflect the size of the object leading to degraded recovery performance.
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Performance/Resource Usage
Target version:
-
% Done:
0%
Source:
Tags:
backport_processed
Backport:
quincy, reef
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
OSD
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Currently, PullOp cost is set to the following:
uint64_t PullOp::cost(CephContext *cct) const
{
return cct->_conf->osd_push_per_object_cost +
cct->_conf->osd_recovery_max_chunk;
}
In addition, the cost could be further aggregated based on the
number of PullOp items in MOSDPGPull message.
However, PushOp cost appears to reflect a little over the object size and
therefore, this may not need any change for mClock but will need to
be verified.
Updated by Sridhar Seshasayee about 1 year ago
- Status changed from New to Fix Under Review
- Pull request ID set to 49975
Updated by Sridhar Seshasayee 9 months ago
- Status changed from Fix Under Review to Pending Backport
- Backport set to quincy, reef
Updated by Backport Bot 9 months ago
- Copied to Backport #62133: reef: osd: PushOp and PullOp costs for mClock don't reflect the size of the object leading to degraded recovery performance. added
Updated by Backport Bot 9 months ago
- Copied to Backport #62134: quincy: osd: PushOp and PullOp costs for mClock don't reflect the size of the object leading to degraded recovery performance. added
Updated by Sridhar Seshasayee 9 months ago
- Status changed from Pending Backport to Resolved
Actions