[Database] Disable read-ahead to prevent thrashing
AbandonedPublic

Authored by hurikhan77 on Oct 10 2019, 5:32 PM.

Details

Reviewers
ngraham
Summary

Prevent filesystem thrashing in low-mem situations by turning off
read-ahead. Access patterns of baloo are unlikely to benefit from
read-ahead and preserving cache is more valuable than reading ahead
potentially unused data.

In low-memory conditions, the random access patterns of Baloo combined
with read-ahead tend to dominate the cache. Let Baloo be the slow player
here, and leave system cache and memory for interactive performance.

Diff Detail

Repository
R293 Baloo
Lint
Lint Skipped
Unit
Unit Tests Skipped
hurikhan77 created this revision.Oct 10 2019, 5:32 PM
Restricted Application added a project: Frameworks. · View Herald TranscriptOct 10 2019, 5:32 PM
Restricted Application added subscribers: Baloo, kde-frameworks-devel. · View Herald Transcript
hurikhan77 requested review of this revision.Oct 10 2019, 5:32 PM
hurikhan77 updated this revision to Diff 67627.Oct 10 2019, 5:35 PM
hurikhan77 retitled this revision from [Database] Rework handling environment flags to [Database] Disable read-ahead to prevent thrashing.
hurikhan77 edited the summary of this revision. (Show Details)

Prevent filesystem thrashing in low-mem situations by turning off
read-ahead. Access patterns of baloo are unlikely to benefit from
read-ahead and preserving cache is more valuable than reading ahead
potentially unused data.

In low-memory conditions, the random access patterns of Baloo combined
with read-ahead tend to dominate the cache. Let Baloo be the slow player
here, and leave system cache and memory for interactive performance.

hurikhan77 abandoned this revision.Oct 10 2019, 5:38 PM

My submission didn't work as expected...