Lines Matching full:bidirectional
48 * Using Netperf to Measure Bidirectional Transfer::
2406 @node Using Netperf to Measure Aggregate Performance, Using Netperf to Measure Bidirectional Transfer, Using Netperf to Measure Request/Response , Top
2611 single-connection, bidirectional bulk-transfer test. When run with
2898 @node Using Netperf to Measure Bidirectional Transfer, The Omni Tests, Using Netperf to Measure Aggregate Performance, Top
2900 @chapter Using Netperf to Measure Bidirectional Transfer
2903 bidirectional transfer. The first is to run concurrent netperf tests
2917 * Bidirectional Transfer with Concurrent Tests::
2918 * Bidirectional Transfer with TCP_RR::
2922 @node Bidirectional Transfer with Concurrent Tests, Bidirectional Transfer with TCP_RR, Using Netperf to Measure Bidirectional Transfer, Using Netperf to Measure Bidirectional Transfer
2924 @section Bidirectional Transfer with Concurrent Tests
2979 @node Bidirectional Transfer with TCP_RR, Implications of Concurrent Tests vs Burst Request/Response, Bidirectional Transfer with Concurrent Tests, Using Netperf to Measure Bidirectional Transfer
2981 @section Bidirectional Transfer with TCP_RR
2990 single-connection bidirectional transfer than a simple
3011 to get a bidirectional bulk-throughput result. As one can see, the -v
3028 @node Implications of Concurrent Tests vs Burst Request/Response, , Bidirectional Transfer with TCP_RR, Using Netperf to Measure Bidirectional Transfer
3033 bidirectional performance.
3045 not), however, with just a single, bidirectional request/response test
3052 Also, with a bidirectional request/response test there is something of
3062 @node The Omni Tests, Other Netperf Tests, Using Netperf to Measure Bidirectional Transfer, Top
