Diff: LinuxIoScheduler

Differences between current version and predecessor to the previous major change of LinuxIoScheduler.

Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History

Newer page: version 17 Last edited on Sunday, July 22, 2012 6:11:04 pm by RonnieCollinson
Older page: version 16 Last edited on Thursday, December 16, 2010 8:04:51 pm by JohnMcPherson Revert
@@ -43,8 +43,10 @@
 !! Which one should I use? 
 I've not personally done any testing on this, so I can't speak from experience yet. The anticipatory scheduler will be the default one for a reason however - it is optimised for the common case. If you've only got single disk systems (ie, no RAID - hardware or software) then this scheduler is probably the right one for you. If it's a multiuser system, you will probably find CFQ or deadline providing better performance, and the numbers seem to back deadline giving the best performance for database systems. 
+The noop scheduler has minimal cpu overhead in managing the queues and may be well suited to systems with either low seek times, such as an SSD or systems using a hardware RAID controller, which often has its own IO scheduler designed around the RAID semantics.  
 !! Tuning the I/O schedulers 
 The schedulers may have parameters that can be tuned at runtime. Read the LinuxKernel documentation on the schedulers listed in the ''References'' section below