Presentation is loading. Please wait.

Presentation is loading. Please wait.

A special acknowledge goes to J.F Kurose and K.W. Ross Some of the slides used in this lecture are adapted from their original slides that accompany the.

Similar presentations


Presentation on theme: "A special acknowledge goes to J.F Kurose and K.W. Ross Some of the slides used in this lecture are adapted from their original slides that accompany the."— Presentation transcript:

1 A special acknowledge goes to J.F Kurose and K.W. Ross Some of the slides used in this lecture are adapted from their original slides that accompany the book “Computer Networking, A Top-Down Approach” All material copyright 1996-2009 J.F Kurose and K.W. Ross, All Rights Reserved CS 283Computer Networks Spring 2012 Instructor: Yuan Xue

2 Overview  Project Release  Review: Protocol stack  Performance metrics  DETERlab tutorial  Coming up  Socket programming  Lab 1 release

3 Internet protocol stack  application: supporting network applications  FTP, SMTP, HTTP  transport: process-process data transfer  TCP, UDP  network: routing of datagrams from source to destination  IP, routing protocols  link: data transfer between neighboring network elements  Ethernet, 802.111 (WiFi), PPP  physical: bits “on the wire” application transport network link physical

4 Understanding and Measure Internet Performance

5 How do loss and delay occur? packets queue in router buffers  packet arrival rate to link exceeds output link capacity  packets queue, wait for turn A B packet being transmitted (delay) packets queueing (delay) free (available) buffers: arriving packets dropped (loss) if no free buffers

6 Four sources of packet delay d proc : nodal processing  check bit errors  determine output link  typically < msec A B propagation transmission nodal processing queueing d queue : queueing delay  time waiting at output link for transmission  depends on congestion level of router d nodal = d proc + d queue + d trans + d prop d trans : transmission  Recall its calculation

7 Four sources of packet delay A B propagation transmission nodal processing queueing d nodal = d proc + d queue + d trans + d prop d trans : transmission delay:  L: packet length (bits)  R: link bandwidth (bps)  d trans = L/R d prop : propagation delay:  d: length of physical link  s: propagation speed in medium (~2x10 8 m/sec)  d prop = d/s d trans and d prop very different

8 “Real” Internet delays and routes  What do “real” Internet delay & loss look like?  Traceroute program: provides delay measurement from source to router along end-end Internet path towards destination. For all i:  sends three packets that will reach router i on path towards destination  router i will return packets to sender  sender times interval between transmission and reply. 3 probes

9 Packet loss  queue (aka buffer) preceding link in buffer has finite capacity  packet arriving to full queue dropped (aka lost)  lost packet may be retransmitted by previous node, by source end system, or not at all A B packet being transmitted packet arriving to full buffer is lost buffer (waiting area)

10 Throughput  throughput: rate (bits/time unit) at which bits transferred between sender/receiver  instantaneous: rate at given point in time  average: rate over longer period of time server, with file of F bits to send to client link capacity R s bits/sec link capacity R c bits/sec server sends bits (fluid) into pipe pipe that can carry fluid at rate R s bits/sec) pipe that can carry fluid at rate R c bits/sec)

11 Throughput (more)  R s < R c What is average end-end throughput? R s bits/sec R c bits/sec  R s > R c What is average end-end throughput? R s bits/sec R c bits/sec link on end-end path that constrains end-end throughput bottleneck link

12 Throughput: Internet scenario 10 connections (fairly) share backbone bottleneck link R bits/sec RsRs RsRs RsRs RcRc RcRc RcRc R  per-connection end-end throughput: min(R c,R s,R/10)  in practice: R c or R s is often bottleneck

13 Throughput (more)  If the sender sends the data at R s bits/sec, but the receiver receives the data at R r bits/sec (< R s bits/sec), where is the rest of data?  Can a sender ask for a reliable data transfer service at rate R s bits/sec on Internet?  How can I measure the maximum possible throughput for my application(flow/traffic)?


Download ppt "A special acknowledge goes to J.F Kurose and K.W. Ross Some of the slides used in this lecture are adapted from their original slides that accompany the."

Similar presentations


Ads by Google