You are not logged in.

#1 2008-07-28 02:18:53

fukawi2
Ex-Administratorino
From: .vic.au
Registered: 2007-09-28
Posts: 6,223
Website

Why Deadline Scheduler for JFS

According to the Wiki, using the Deadline Scheduler is supposed to improve the performance of JFS (http://wiki.archlinux.org/index.php/JFS … _Scheduler)

Knowing not much about I/O schedulers, I went in pursuit of information... Reading the article below, I can't quite understand how Deadline would improve performance of the Anticipatory Scheduler?
http://www.linuxjournal.com/article/6931

This didn't shed much light that wasn't in the first article either:
http://www.wlug.org.nz/LinuxIoScheduler

Does anyone have an explanation for why Deadline would improve performance on JFS? Why would the 6ms pause while waiting for more read requests outbalance the extra seek times?

Offline

#2 2008-07-28 04:27:01

theringmaster
Member
From: Air Force
Registered: 2007-07-16
Posts: 581
Website

Re: Why Deadline Scheduler for JFS


Check me out on twitter!!! twitter.com/The_Ringmaster

Offline

#3 2008-07-28 05:51:56

fukawi2
Ex-Administratorino
From: .vic.au
Registered: 2007-09-28
Posts: 6,223
Website

Re: Why Deadline Scheduler for JFS

The first article I linked to explained it all pretty well; I'm understanding the differences between the schedulers, but I'm not understanding how JFS is making the DS better than the AS...

Offline

#4 2008-08-01 12:51:01

BJJ
Member
Registered: 2007-10-23
Posts: 25

Re: Why Deadline Scheduler for JFS

http://en.wikipedia.org/wiki/JFS_(file_system)

It looks like JFS already has a own form of 'anticipation'.
See the sections Concurrent Input / Output (CIO) and Allocation Groups.

Another anticipator like AS would only increase overhead, therefore deadline would work beter.

Offline

#5 2008-08-01 14:13:04

jleach
Member
Registered: 2008-07-24
Posts: 27

Re: Why Deadline Scheduler for JFS

One of the shortcomings of the anticipatory scheduler is that it assumes only 1 physical reading head, only 1 read request is dispatched to the disk controller at a time, and read anticipation assumes synchronous requests are issued by individual processes.

This makes it weaker for RAID systems, which I assume is generally where the talk of "deadline is superior for filesystem X" comes up.

In truth CFQ and deadline have similar results.  Beyond that one would be comparing filesystems, and though I use and like JFS, it's not regarded as the fastest.

Other info:
http://www.cs.ccu.edu.tw/~lhr89/linux-k … dulers.pdf
http://edgyu.excess.org/ols/2004/Steven … dulers.pdf

Offline

#6 2008-08-02 03:07:31

fukawi2
Ex-Administratorino
From: .vic.au
Registered: 2007-09-28
Posts: 6,223
Website

Re: Why Deadline Scheduler for JFS

Thanks guys smile
There's some good info in that, cheers

Offline

Board footer

Powered by FluxBB