ndt-dev - [ndt-dev] [ndt] r650 committed - Extended the description of the S2C known limitation.
Subject: NDT-DEV email list created
List archive
[ndt-dev] [ndt] r650 committed - Extended the description of the S2C known limitation.
Chronological Thread
- From:
- To:
- Subject: [ndt-dev] [ndt] r650 committed - Extended the description of the S2C known limitation.
- Date: Wed, 21 Sep 2011 19:28:20 +0000
Revision: 650
Author:
Date: Wed Sep 21 12:27:31 2011
Log: Extended the description of the S2C known limitation.
http://code.google.com/p/ndt/source/detail?r=650
Modified:
/wiki/NDTTestMethodology.wiki
=======================================
--- /wiki/NDTTestMethodology.wiki Wed Sep 21 12:20:42 2011
+++ /wiki/NDTTestMethodology.wiki Wed Sep 21 12:27:31 2011
@@ -145,7 +145,7 @@
==== Known Limitations (Server-To-Client Throughput Test) ====
-A 10 second test may not be enough time for TCP to reach a steady-state on a high bandwidth, high latency link.
+A 10 second test may not be enough time for TCP to reach a steady-state on a high bandwidth, high latency link. However, the increased information that the web100 variables provide could be used to answer this question. Thus the NDT server could detect and report if something was preventing the system from fully utilising the link. For example tracking how long slow start ran and what the maximum CWND value was can tell us if the connection was network limited or configuration limited. On a transatlantic 10 Gbps link slow start should run for about 3 seconds and CWND should indicate the speed peaked at 10 Gbps.
== Specific Detection Algorithms/Heuristics ==
- [ndt-dev] [ndt] r650 committed - Extended the description of the S2C known limitation., ndt, 09/21/2011
Archive powered by MHonArc 2.6.16.