Use BFQ I/O scheduler for spinning disks

It offers much better latency in exchange for only a modest reduction
in throughput, and only for some workflows. High latency being a
defining negative characteristic of spinning disks, this seems like a
worthwhile trade-off for us to make for desktop usage.

This doesn't change the default I/O schedulers for flash-based storage,
as the defaults seem sensibly chosen (`none` for NVMe SSDs and
`mq-deadline` for everything else).

Related to #258
This commit is contained in:
Nate Graham
2025-08-29 07:50:16 -06:00
parent abc0adc66d
commit 0ff55a9698

View File

@@ -0,0 +1,6 @@
# SPDX-License-Identifier: GPL-2.0-only OR GPL-3.0-only OR LicenseRef-KDE-Accepted-GPL
# SPDX-FileCopyrightText: none
# Use BFQ I/O scheduler for spinning disks, as it offers much better latency in
# exchange for only a modest reduction in throughput, and only for some workflows
ACTION=="add|change", KERNEL=="sd[a-z]*", ATTR{queue/rotational}=="1", ATTR{queue/scheduler}="bfq"