You are not logged in.
Pages: 1
From what I read on Arch Wiki and Wikipedia about schedulers, it seems NOOP is recommended for SSD's because:
NOOP scheduler is best used with solid state devices such as flash memory or in general with devices that do not depend on mechanical movement to access data (meaning typical "hard disk" drive technology consisting of seek time primarily, plus rotational latency). Such non-mechanical devices do not require re-ordering of multiple I/O requests, a technique that groups together I/O requests that are physically close together on the disk, thereby reducing average seek time and the variability of I/O service time
But for normal HDD's (wo RAID) its not so clear, can I say Deadline will be suggested as it enforces a deadline thus "minimum performance"? Or keep with the default CFQ?
Computer Science Student, Web Developer
Offline
http://www.danielscottlawrence.com/shou … or-my-ssd/
You'll get a tiny benefit switching to noop - but cfq detects and does all of the right things on non rotational disks nowadays so I just leave it as it.
Offline
I would stay with CFQ
heres more benchmarks: http://www.phoronix.com/scan.php?page=a … 2012&num=2
Asus M4A785TD-V ;; Phenom II X4 @ 3.9GHz ;; Ripjaws 12GB DDR3-1600 ;; 128GB Samsung 830 ;; MSI GTX460 v2 w/ blob ;; Arch Linux + KDE 4.x
Offline
Pages: 1