Actions
Feature #21849
closedsparse-reads should not be used for small IO requests
Status:
Resolved
Priority:
Normal
Assignee:
Jason Dillaman
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
luminous
Reviewed:
Affected Versions:
Pull request ID:
Description
There is a larger time and space overhead for performing a sparse read so it should be avoided for small IO. Backend support for sparse-read is disabled by default for filestore, and bluestore defaults to 16K allocations for SSDs and 64K allocations for HDDs. Perhaps it would be simplest to just restrict sparse-read to only the cases where the full object is being read and provide an advanced-level config override to lower the requirement if needed.
Actions