Originally posted by Shnatsel
View Post
Announcement
Collapse
No announcement yet.
Linux 4.17 I/O Scheduler Tests On An NVMe SSD Yield Surprising Results
Collapse
X
-
- Likes 2
-
Originally posted by Shnatsel View PostWhat happened to CFQ? Last time I checked that was the default for HDDs and one of the most common schedulers out there. It's very strange to see it omitted from the comparison.
BFQ is the multi-queue replacement for CFQ and is good for almost all devices. Kyber keeps NVMe responsive under heavy IO load by keeping the queue depth managable so high priority IO doesn't have to wait too long. Important since NVMe queues can, in theory (there's usually hardware limits), grow to 65535 in length under the "none" scheduler.
- Likes 4
Leave a comment:
-
Originally posted by edwaleni View PostWhat was the block size used on the Optane? If you published it, I didn't see it, (sorry)
- Likes 2
Leave a comment:
-
What was the block size used on the Optane? If you published it, I didn't see it, (sorry)
Leave a comment:
-
What happened to CFQ? Last time I checked that was the default for HDDs and one of the most common schedulers out there. It's very strange to see it omitted from the comparison.
- Likes 2
Leave a comment:
-
how to enable the low_latency property of BFQ? module parameter? sysfs? sysctl? where?
- Likes 2
Leave a comment:
-
Intel Optane is a really niche NVMe though. May be tests with recent Samsung 970 Evo or WD Black NVMe would be more relevant for most users.
- Likes 2
Leave a comment:
-
Linux 4.17 I/O Scheduler Tests On An NVMe SSD Yield Surprising Results
Phoronix: Linux 4.17 I/O Scheduler Tests On An NVMe SSD Yield Surprising Results
With the Linux 4.17 kernel soon to be released, I've been running some fresh file-system and I/O scheduler tests -- among other benchmarks -- of this late stage kernel code. For your viewing pleasure today are tests of a high performance Intel Optane 900p NVMe SSD with different I/O scheduler options available with Linux 4.17.
Tags: None
Leave a comment: