The Gateway to Computer Science Excellence
First time here? Checkout the FAQ!
+27 votes

Consider a disk with the $100$ tracks numbered from $0$ to $99$ rotating at $3000$ rpm. The number of sectors per track is $100$ and the time to move the head between two successive tracks is $0.2$ millisecond.

  1. Consider a set of disk requests to read data from tracks $32, 7, 45, 5$ and $10$. Assuming that the elevator algorithm is used to schedule disk requests, and the head is initially at track $25$ moving up (towards larger track numbers), what is the total seek time for servicing the requests?
  2. Consider an initial set of $100$ arbitrary disk requests and assume that no new disk requests arrive while servicing these requests. If the head is initially at track $0$ and the elevator algorithm is used to schedule disk requests, what is the worse case time to complete all the requests?
asked in Operating System by Veteran (59.8k points)
edited by | 2.5k views

3 Answers

+22 votes
Best answer

Answer for (A):

We are using SCAN - Elevator algorithms.

We will need to go from $25\rightarrow 99 \rightarrow  5$. (As we will move up all the way to $99$,servicing all request, then come back to $5$.)

So, total seeks $= 74+94= 168$

Total time $= 168 \times 0.2 = 33.60000$

Answer for (B):

We need to consider rotational latency too $\rightarrow $

$3000$ rpm

I.e. $50$ rps

$1 \ r = 1000 /50 \ msec = 20 \ msec$

So, rotational latency $= 20/2 = 10 \ msec$ per access.

In worst case we need to go from tracks $0-99.$ I.e. $99$ seeks

Total time $= 99  \times 0.2 + 10 \times 100  = 1019.8 \ msec = 1.019 \ sec$

answered by Boss (43.6k points)
edited by

what is the worse case time to complete all the requests?

Hi Guys,

I think instead of average rotational latency we should take time taken in full rotation. What is your opinion ?

If we are taking rotational latency because of "we do not know which sector is to be selected in those 100 random track request", then also in part - a) if request completion time asked instead of "seek time" then we have to consider the same avg. rotational latency in addition?
@bruv depends on question
One thing to notice here

request should go from 25 ->99 ->10

isnot it?

why upto 5 track request is taking?

Is there calculation mistake or am I missing somewhere?

Plz chk

@srestha ji, 

Is there calculation mistake 


am I missing somewhere?



25 ->99 ->5 .Means staring from 25 goto 99 and service all request and come back to 5 ans service all request on the way.
In the worst case, can the requests come in the form - 0, 99, 0, 99 .... so on. In that case for every two requests 99 seek would be needed. Correct me If I am wrong here...
Why 99 seeks ?

In worst case

Request can be from tracks

0, 99, 1, 98,...

Plz clarify.
because it is elevator algortihm wont follow the order of goes in a flow...till end and come back
NO not at all
–3 votes


end track: 99


total seeks=(99-25)+(99-5)=74+94=168

total seek time = 0.2 * 168 ms


from 0 to 99

worst case time = 0.2 * 99 ms
answered by Loyal (8.1k points)
You missed rotational latency
–3 votes

Question is about how much time required to satisfied 100  requests...

1 request time is = Tseek +TrotLatency + data transfer time

Datatransfer time = 0(as not given any info)

99 seeks and 100 rotations required in worst case...

So 99 * seek time + 100*rotational latency...
answered by Junior (609 points)

Related questions

Quick search syntax
tags tag:apple
author user:martin
title title:apple
content content:apple
exclude -tag:apple
force match +apple
views views:100
score score:10
answers answers:2
is accepted isaccepted:true
is closed isclosed:true
50,115 questions
53,224 answers
70,473 users