Skip to content

C
csci363
Commit 54169e32 authored by wx002's avatar wx002
Browse files
Options

Update readme.txt

parent af4b01ee
Hide whitespace changes
Inline Side-by-side
Showing with 95 additions and 0 deletions
proj1_rdt/readme.txt → proj1_rdt/readme.md
View file @ 54169e32
This is implementation of RDT (Reliable Data Transfer) protocol over UDP. This is implementation of RDT (Reliable Data Transfer) protocol over UDP.
Running instructions: Running instructions:
0. Run udp_box.py with respective commandline arguments. addr=127.0.0.1, port=8880, remote_port=8888 0. Run udp_box.py with respective commandline arguments. addr=127.0.0.1, port=8880, remote_port=8888
1. Run recv.py. Parameters: --addr (the address to listen to, default=127.0.0.1), --port (the port to listen to, default=8888) 1. Run recv.py. Parameters: --addr (the address to listen to, default=127.0.0.1), --port (the port to listen to, default=8888)
2. run sender.py. Parameters: --remote_addr(the remote address to send file to, default=127.0.0.1), --remote_port (the remote port to send file to, default=8880), --file (the file that will be sending, default=sendData/alice.txt) 2. run sender.py. Parameters: --remote_addr(the remote address to send file to, default=127.0.0.1), --remote_port (the remote port to send file to, default=8880), --file (the file that will be sending, default=sendData/alice.txt)
Note: Note:
-SendData: File to send should be located in here -SendData: File to send should be located in here
-recvData: The file received will be located here, named recv.txt -recvData: The file received will be located here, named recv.txt
The default configuration is meant to run with the udp_box, in the following configuration: The default configuration is meant to run with the udp_box, in the following configuration:
sender.py <-> udp_box.py <-> recv.py sender.py <-> udp_box.py <-> recv.py
Basic benchmark using udp_box: Basic benchmark using udp_box:
conditions: conditions:
- 50kbs bandwidth - 50kbs bandwidth
- Sending file: Alice.txt, size=167546 bytes - Sending file: Alice.txt, size=167546 bytes
- parameters: loss rate, out of order rate(ooo_rate), duplicate packet rate(dupe_rate), byte error rate(ber) - parameters: loss rate, out of order rate(ooo_rate), duplicate packet rate(dupe_rate), byte error rate(ber)
Tested with 4 conditions (Ideal, good, medium, and terrible) Tested with 4 conditions (Ideal, good, medium, and terrible)
Ideal: (--loss_rate 0 --ooo_rate 0 --dupe_rate 0 --ber 0) Ideal: (--loss_rate 0 --ooo_rate 0 --dupe_rate 0 --ber 0)
- time: 118.819721s - time: 118.819721s
- transfer rate: 1410.0857887050586 bytes per second - transfer rate: 1410.0857887050586 bytes per second
Good: (--loss_rate 0.01 --ooo_rate 0.01 --dupe_rate 0.01 --ber 1e-8) Good: (--loss_rate 0.01 --ooo_rate 0.01 --dupe_rate 0.01 --ber 1e-8)
- time: 1239.808353s - time: 1239.808353s
- transfer rate: 135.1386281553791 bytes per second - transfer rate: 135.1386281553791 bytes per second
Medium: (--loss_rate 0.02 --ooo_rate 0.02 --dupe_rate 0.02 --ber 1e-6): Medium: (--loss_rate 0.02 --ooo_rate 0.02 --dupe_rate 0.02 --ber 1e-6):
- time: 2393.281579s - time: 2393.281579s
- transfer rate: 70.00680633241944 bytes per second - transfer rate: 70.00680633241944 bytes per second
Terrible: (--loss_rate 0.1 --ooo_rate 0.03 --dupe_rate 0.05 --ber 1e-3): Terrible: (--loss_rate 0.1 --ooo_rate 0.03 --dupe_rate 0.05 --ber 1e-3):
- time: Infinity - time: Infinity
- transfer rate: SLOW - transfer rate: SLOW
Pros: Pros:
- Ensures data is correctly transferee - Ensures data is correctly transferee
- There is almost no chance of data error - There is almost no chance of data error
- Packets arrive in sequential order - Packets arrive in sequential order
- Very reliable when the connection is decent, performs well within reasonable amount of time - Very reliable when the connection is decent, performs well within reasonable amount of time
- Will be able to run and sustain even under terrible conditions, with almost no data error - Will be able to run and sustain even under terrible conditions, with almost no data error
Cons: Cons:
- It is not using the maximum bandwidth at all - It is not using the maximum bandwidth at all
- Transfer rate is very low since is sending lines - Transfer rate is very low since is sending lines
- It require insane amount of time with non ideal conditions - It require insane amount of time with non ideal conditions
- Under terrible conditions, the transfer will last indefinitely - Under terrible conditions, the transfer will last indefinitely
- Not taking advantage of the full bandwidth - Not taking advantage of the full bandwidth
Possible additions: Possible additions:
- Add initial handshakes for the receiver to know what to name the file - Add initial handshakes for the receiver to know what to name the file
- Add timeout phase to break out indefinite run times with terrible connection - Add timeout phase to break out indefinite run times with terrible connection
- Consider revamping the algorithm to use more bandwidth - Consider revamping the algorithm to use more bandwidth
Protocol sequence diagram: Protocol sequence diagram:
Sender Receiver Sender Receiver
| ---------------line 0------------------> | | ---------------line 0------------------> |
| <--------------ACK for line 0----------- | | <--------------ACK for line 0----------- |
| ---------------line 1------------------> | | ---------------line 1------------------> |
| <--------------ACK for line 1----------- | | <--------------ACK for line 1----------- |
| ---------------line 2------------------> | | ---------------line 2------------------> |
| <--------------ACK for line 2----------- | | <--------------ACK for line 2----------- |
| ---------------line 3------------------> | | ---------------line 3------------------> |
| <--------------ACK for line 3----------- | | <--------------ACK for line 3----------- |
| ---------------line 4------------------> | | ---------------line 4------------------> |
| <--------------ACK for line 4----------- | | <--------------ACK for line 4----------- |
| ---------------line 4------------------> | | ---------------line 4------------------> |
| <--------------ACK for line 4----------- | | <--------------ACK for line 4----------- |
| ---------------line 5------------------> | | ---------------line 5------------------> |
| <--------------ACK for line 5----------- | | <--------------ACK for line 5----------- |
| ---------------line 6------------------> | | ---------------line 6------------------> |
| <--------------ACK for line 6----------- | | <--------------ACK for line 6----------- |
| ---------------line 7------------------> | | ---------------line 7------------------> |
| <--------------ACK for line 7----------- | | <--------------ACK for line 7----------- |
| ---------------line 8------------------> | | ---------------line 8------------------> |
| <--------------ACK for line 8----------- | | <--------------ACK for line 8----------- |
| ---------------END ------------------> | | ---------------END ------------------> |
| <--------------END---------------------- | | <--------------END---------------------- |
Sender Receiver Sender Receiver
Packet structure: Packet structure:
Each packet is representing a line of the file. Header is the index. All packets arrive at sequential order. Each packet is representing a line of the file. Header is the index. All packets arrive at sequential order.
structure: encoded Header + \t + encoded string + \t + raw data string structure: encoded Header + \t + encoded string + \t + raw data string
Encoded Header: Encoded Header:
- Index of the packet, encoded using base64 - Index of the packet, encoded using base64
Encoded String: Encoded String:
- The content of the line, encoded using base64 - The content of the line, encoded using base64
Verify Method: Verify Method:
- Header must arrive in order, discard packet if is out of order and wait for resend - Header must arrive in order, discard packet if is out of order and wait for resend
- The decoded encoded string must match the raw data string. Otherwise, packet is corrupted and ask for resend - The decoded encoded string must match the raw data string. Otherwise, packet is corrupted and ask for resend
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment