Changes between Version 18 and Version 19 of MEBSandbox/UDTExample
- Timestamp:
- 05/02/12 14:56:15 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MEBSandbox/UDTExample
v18 v19 35 35 server is ready at port: 9000 36 36 }}} 37 On pc2, start a UDT file transfer client, using this command: 37 38 * On pc2, start a UDT file transfer client, using this command: 38 39 {{{ 39 40 pc2:~% /local/udt4/app/recvfile pc1 9000 /local/datafiles/sm.10M /dev/null … … 44 45 speed = 7.14472Mbits/sec 45 46 }}} 47 46 48 * There are three data files available for transfer tests: '''/local/datafiles/sm.10M''' is 10MB, '''/local/datafiles/med.100M''' is 100MB, and '''/local/datafiles/lg.1G''' is 1GB. Leave your transfer server running on pc1, and try transferring each of these files in turn by typing the appropriate commands on pc2. Keep track of the transfer rates in each case. 49 47 50 * You can leave your UDT server running or stop it with ctrl-C. 48 51 … … 52 55 53 56 * For a TCP-based (FTP) transfer, there's already a FTP server running on pc1. Log into pc2, and start an ftp client: 54 [[br]] 57 55 58 (You type ''ftp pc1'', the user name ''anonymous'', and any password you want, although your e-mail address is traditional.) 59 56 60 {{{ 57 61 pc2:~% ftp pc1 … … 66 70 ftp> 67 71 }}} 72 68 73 * Still on pc2, request a file transfer. Note the reported file size, transfer time, and transfer rate. 74 69 75 {{{ 70 76 ftp> get med.100M … … 75 81 104857600 bytes received in 1.75 secs (58508.9 kB/s) 76 82 }}} 83 77 84 * You can perform additional transfers with additional get commands. When you're done, exit the ftp client with the quit command. 78 85 … … 81 88 In this experiment, you'll be changing the characteristics of the link and measuring how they affect UDT and TCP performance. 82 89 83 * Log into your delay node as you do with any other node. Then, on your delay node, use this command:90 * Log into your delay node as you do with any other node. Then, on your delay node, use this command: 84 91 {{{ 85 92 %sudo ipfw pipe show … … 113 120 114 121 Here are the command sequences you'll need to change your link parameters. 122 In each case, you'll need to provide the correct pipe numbers, if they're different from the example. 115 123 116 124 * To change bandwidth (100M means 100Mbits/s): … … 138 146 }}} 139 147 148 * You can combine settings for bandwidth, delay, and loss by specifying more than one 149 in a single ipfw command. We'll use this form in the procedure below. 150 140 151 == Experiment Procedure == 141 152 142 Set your link parameters to use maximum bandwidth, no delay, no packet loss:153 * Set your link parameters to use maximum bandwidth, no delay, no packet loss: 143 154 144 155 {{{ … … 147 158 }}} 148 159 149 Verify with 160 * Verify with 161 150 162 {{{ 151 163 sudo ipfw pipe show … … 157 169 0 ipv6-icmp 1610612736 ::/0 ff02::1:ff79:29fb/0 5 378 0 0 0 158 170 }}} 171 172 Note that bandwidth is set to ''unlimited'', delay to ''0 ms'', and no PLR is shown. 173 174 * Using this initial setting, try a few UDT transfers, including the larger files. Now try FTP transfers. Record the transfer sizes and rates. 175 176 * Now change the link parameters to reduce the available bandwidth to 10Mbps: 177 178 {{{ 179 sudo ipfw pipe 60111 config bw 10M delay 0 plr 0 180 sudo ipfw pipe 60121 config bw 10M delay 0 plr 0 181 }}} 182 183 * Repeat your file transfers with the new settings. As before, note the transfer sizes and rates, as well as the link settings.