| Real Wildblue Pings Pinging the proxy in Wildblue's Riverside Gateway using a Wildblue system while all other tasks in my computer are idle:
ping -n 20 -w 8000 12.213.224.60
Reply from 12.213.224.60: bytes=32 time=1105ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1123ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1226ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1106ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1166ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1147ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1087ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1122ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1193ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1078ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1138ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1084ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1107ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1112ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1124ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1139ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1147ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1115ms TTL=58
Reply from 12.213.224.60: bytes=32 time=2421ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1144ms TTL=58
Ping statistics for 12.213.224.60:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1078ms, Maximum = 2421ms, Average = 1194ms
The following pings were collected while loading cnn.com in another task. Notice the latency is as low as 582 ms under this condition.
ping -n 20 -w 8000 12.213.224.60
Reply from 12.213.224.60: bytes=32 time=1291ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1119ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1152ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1118ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1186ms TTL=58
Reply from 12.213.224.60: bytes=32 time=2567ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1183ms TTL=58
Reply from 12.213.224.60: bytes=32 time=609ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1977ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1331ms TTL=58
Reply from 12.213.224.60: bytes=32 time=582ms TTL=58
Reply from 12.213.224.60: bytes=32 time=787ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1036ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1127ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1168ms TTL=58
Reply from 12.213.224.60: bytes=32 time=720ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1042ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1041ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1101ms TTL=58
Reply from 12.213.224.60: bytes=32 time=1110ms TTL=58
Ping statistics for 12.213.224.60:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 582ms, Maximum = 2567ms, Average = 1162ms
When the DAMA scheduler was implemented in November 2006, the latency reported by pings increased from about 600 ms to 1,200 ms.
Due to a minimum latency of about .5 seconds, geostationary satellite systems will always be slow for real time applications and protocols that require a lot of handshaking, such as secure HTTP. Assertions that it is no good for uploading, download and streaming are completely false. After the transfer is initially set up, the latency is irrelevant. If Wildblue does not pack too many customers onto a spot beam, the system uploads and download near the advertised speeds. My spot beam has never been overloaded.
--
Value Pack, beam 31, Riverside gateway |
