5.
7 IO PERFORMANCE
• I/O performance has measures that have no
counterparts in design.
• One of these is
• Diversity: Which I/O devices can
1. connect to the computer system?
• Capacity: How many I/O devices can
2. connect to a computer system?
MZCET\ECE\4A&B\7SEM\EC6009\ 1
ACA\5
5.7
• In addition to these unique measures the
traditional measures of performance also
apply to I/O.
• I/O throughput is sometimes called I/O
bandwidth and response time is sometimes
called latency.
MZCET\ECE\4A&B\7SEM\EC6009\ 2
ACA\5
5.7
• The simple producer-server model.
• The producer creates tasks to be performed
and places them in a buffer the server takes
tasks from the first in, first out buffer and
performs them.
MZCET\ECE\4A&B\7SEM\EC6009\ 3
ACA\5
5.7
• The buffer until the server finishes the task.
• Throughput is simply the average number of
tasks completed by the server over a time
period.
• To get the highest possible throughput, the
server should never be idle thus the buffer
should never be empty.
MZCET\ECE\4A&B\7SEM\EC6009\ 4
ACA\5
5.7
• Response time on the other hand counts time
spent in the buffer so an empty buffer shrinks
it.
• Another measure of I/O performance is the
interference of I/O with processor execution.
• Transferring data may interfere with the
execution of another process.
MZCET\ECE\4A&B\7SEM\EC6009\ 5
ACA\5
5.7
• There is also overhead due to handling I/O
interrupts.
• Our concern here is how much longer a
process will take because of I/O for another
process.
MZCET\ECE\4A&B\7SEM\EC6009\ 6
ACA\5
5.7
Throughput versus Response Time
• Figure shows throughput versus response
time (or latency) for a typical I/O system.
• The knee of the curve is the area where a little
more throughput results in much longer
response time or
• Conversely a little shorter response time
results in much lower throughput.
MZCET\ECE\4A&B\7SEM\EC6009\ 7
ACA\5
5.7
How does the architect balance these
conflicting demands?
• If the computer is interacting with human
beings.
An interaction or transaction with a computer is
divided into three parts:
MZCET\ECE\4A&B\7SEM\EC6009\ 8
ACA\5
5.7
• Entry time - The time for the user to
1. enter the command.
• System response time - The time
between when the user enters the
command and the complete response
2. is displayed.
• Think time - The time from the
3. reception of the response until the user
begins to enter the next command.
MZCET\ECE\4A&B\7SEM\EC6009\ 9
ACA\5
5.7
• The sum of these three parts is called the
transaction time.
• Several studies report that user productivity is
inversely proportional to transaction time.
MZCET\ECE\4A&B\7SEM\EC6009\ 10
ACA\5
5.7
MZCET\ECE\4A&B\7SEM\EC6009\ 11
ACA\5