20.11.2012 Views

Contents Telektronikk - Telenor

Contents Telektronikk - Telenor

Contents Telektronikk - Telenor

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ent on the window size the user data<br />

size giving peak performance varies.<br />

- The form of the throughput graph<br />

shows that the measured throughput<br />

increases with increasing user data<br />

sizes. Thus, the segment dependent<br />

overhead is reduced when transmitting<br />

fewer segments. After an initial phase,<br />

the measured throughput is more or<br />

less independent of increasing the user<br />

data size. However, for larger window<br />

sizes, the measured throughput decreases<br />

with larger user data sizes.<br />

- All window sizes have their anomalies,<br />

i.e. peaks and drops, for certain user<br />

data sizes.<br />

- The receiver is heavier loaded than the<br />

sender.<br />

5.1 Throughput dependent on<br />

user data size<br />

From Figure 7 (a) it is evident that the<br />

throughput is not indifferent to the user<br />

data size. For a given number of bytes to<br />

be transferred, the smaller the user data<br />

size of the write system call, the more<br />

system calls need to be performed. This<br />

affects the achievable throughput in two<br />

ways. One is due to the processing<br />

resources to do many system calls, the<br />

other is due to a lower average size of the<br />

protocol segments transmitted on the<br />

connection. Therefore, for small user<br />

data sizes increasing the user data size<br />

will increase the throughput. The increase<br />

in throughput flattens when an<br />

increase in user data size does not significantly<br />

influence the average segment size<br />

of the connection.<br />

For 4k, 8k, and 16k window sizes the<br />

throughput is more or less independent of<br />

large user data sizes. It is the window<br />

size and host processing capacity which<br />

are the decisive factors on the overall<br />

throughput. On the contrary, larger window<br />

sizes experience a light degradation<br />

in throughput. The throughput degradation<br />

is caused by acknowledgments being<br />

returned relatively late. The larger the<br />

receive user buffer, the more bytes from<br />

the socket buffer can be copied before an<br />

acknowledgment is returned. Therefore,<br />

the average time to acknowledge each<br />

byte is a little longer, and the throughput<br />

degrades.<br />

For small and large user data sizes the<br />

throughput may be increased if, independent<br />

of the send user data size, the<br />

size of the receive user buffer is fixed.<br />

For small user data sizes a larger receive<br />

buffer reduces the number of read system<br />

Throughput [Mbit/s]<br />

Throughput [Mbit/s]<br />

Throughput [Mbit/s]<br />

30<br />

25<br />

20<br />

15<br />

30<br />

20<br />

10<br />

0<br />

30<br />

20<br />

10<br />

Points discussed in the text<br />

0 4096 8192 12288 16384 20480 24576 28672 32768<br />

0<br />

0 16384 32768 49152 65536<br />

Window size [byte]<br />

(b)Througput dependent on window size<br />

User data size [byte]<br />

(a) TCP throughput dependent on window and user data size<br />

CPU utilization [%]<br />

100<br />

75<br />

50<br />

25<br />

Transmit<br />

Receive<br />

4096 byte window<br />

8192 byte window<br />

16384 byte window<br />

24576 byte window<br />

32768 byte window<br />

40960 byte window<br />

52428 byte window<br />

0<br />

0 16384 32768 49152 65536<br />

Window size [byte]<br />

(c) CPU utilization<br />

Figure 7 Sparc2 SBA-100, network driver version 2.2.6<br />

32768 byte window<br />

32768 byte window, 8192 byte user data receive buffer<br />

0 4096 8192 12288 16384 20480 24576 28672 32768<br />

User data size [byte]<br />

Figure 8 Throughput<br />

changes with a fixed size<br />

receive user buffer<br />

161

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!