190 likes | 313 Views
Transmitting and Tracking Packets of Data Through The TCP and UDP Network Protocols. Todd Deshane Ashwin Venkatraman McNair Program Clarkson University. Overview . Transmission Control Protocol (TCP) User Datagram Protocol (UDP) Research questions and methodology
E N D
Transmitting and Tracking Packets of Data Through The TCP and UDP Network Protocols Todd Deshane Ashwin Venkatraman McNair Program Clarkson University
Overview • Transmission Control Protocol (TCP) • User Datagram Protocol (UDP) • Research questions and methodology • Data analysis and conclusions
Internet Protocols user X English user Y e-mail client SMTP e-mail server TCP/UDP server TCP/UDP TCP/UDP server IP server IP IP server ethernet driver/card IEEE 802.3 standard ethernet driver/card electric signals CS454 (Computer Communication) Clarkson University, Summer 2002
Hi there Hey there, I am ready for data Sending Data I got it. Ready for more! Transmission Control Protocol (TCP) • Handshaking • Reliable data transfer • Flow Control • Congestion Control Connection-oriented service!
User Datagram Protocol (UDP) • No Handshaking! • No Reliable data transfer • No Flow Control • No Congestion Control Sending data! Sending data! Sending data! Sending data! Connectionless-oriented service!
TCP Elegant Protocol Lots of nice features Slower UDP Barebones Protocol Lacks reliability Faster Research Questions How much do we pay to use TCP? How do we measure performance? What causes the differences in performance?
Measuring Network Traffic • Basic terminology: • Network data represented in packets • Packet sizes represented in bytes • Things to measure: • Elapsed Time • Total data sent … Total received • Effective Throughput (data received/time) • Efficiency (Percent received)
Procedure Transmitter (Client) Receiver (Server) Method • Start Server • Send data to Receiver • Record Statistics
PCATTCP Software Utility • Created by Printing Communications Associates, Inc. (PCAUSA) • Windows version of Test TCP (TTCP) • Bench-marking tool for TCP and UDP • Command-line based • Modified to: • Automate the testing process • Use handshakes between trials • Enhance UDP transfers
Same LAN (inside Clarkson) Same Host (same computer) Same Switch (same lab) LAN to LAN (Clarkson to SUNY Potsdam) LAN to Internet (Clarkson to a Roadrunner service) Note: LAN stands for “Local Area Network” Different PCATTCP Trials
Results LAN to LAN LAN to Internet
Results Same Switch Same LAN
Conclusions • Effective Throughput • UDP is usually higher • 6 times better on same LAN • 2 times better LAN to LAN • TCP is sometimes better • 2 times better on same switch • Slightly better from LAN to Road Runner (large packet sizes) • Efficiency • TCP always has 100% • UDP • Usually near 100% on same switch and LAN • Usually less than 50% from LAN to LAN • Usually less than 10% from LAN to Road Runner
Discussion • Causes of lower throughput with UDP • UDP does not retransmit lost packets • Minimal on same switch and same LAN • Significant from LAN to LAN and LAN to Road Runner • UDP lacks flow control • Has minimal effect on same LAN and switch • Has significant effect from LAN to LAN and LAN to Road Runner • UDP has IP fragmentation • Has significant effect on same switch
Future Plans • Use larger data sets (instead of 8 MB, 1 Gig) • Use our PCATTCP software on Wireless technology • Port our PCATTCP version from Windows to UNIX • Test across platforms
Acknowledgements • Ronald E. McNair Scholars Program • Dr. Jeanna Matthews, Clarkson University • The Computer and Technology Services at SUNY Potsdam