| | 65 | |
| | 66 | = Choosing a Medium Bandwidth Path = |
| | 67 | |
| | 68 | Now repeat the test, but change the line '''hb 10 USD''' to '''hbhl 5 USD''' in the config.txt file. This will cause the path service (PS) to return a path across the high bandwidth but also high latency path. While this path will have worse performance than the HB path, it is more cost effective. |
| | 69 | |
| | 70 | = Choosing a High Bandwidth Path at a Low Bandwidth Price = |
| | 71 | |
| | 72 | As a last test, change the line '''hbhl 5 USD''' to '''hb 1 USD'''. In this case the wrapper will request a high bandwidth path, but will only pay a maximum of 1 USD for such paths. Because the path service does not have any high bandwidth paths to sell at this cheaper price tag (1 USD), the PS will return and error and the wrapper will abort the application. Try this yourself by changing the line to ''hb 1 USD'' and then rerunning the iperf tests. You should see the wrapper library aborting the program because high bandwidth paths cost more than the amount allotted by the user. |
| | 73 | |
| | 74 | |
| | 75 | |
| | 76 | |
| | 77 | To chose (and pay for) a higher bandwidth path (and higher cost), you will need to edit the config.txt file and replace the current policy that prefers low bandwidth paths. In particular, you will need to change the line '''lb 1 USD''' to '''hb 10 USD'''. This tells the wrapper library that you prefer high bandwidth paths for the iperf program and that you are willing to pay 10 USD for the paths you receive. Having changed the policies in config.txt, all you need to do is to return iperf as you did above. |
| | 78 | |
| | 79 | Asking for high bandwidth paths results in the PS returning a high bandwidth path passing through the router HB. As a result, the output from iperf should now jump to be roughly 7-8Mbps. |
