regardtv
Expert Member
Hello All,
I've been asked a few times on performance metrics of the iBurst system. While I'm not sure how this will compare to the rollout version I thought I'd give some quick feedback on ping times;packet loss and throughput.
ping times are directly related to signal quality. The higher the quality the better the ping times. This may also have to do with the error correction mechanisms of the gear.
Ping statistics for 196.31.17.162:
Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 69ms, Maximum = 139ms, Average = 75ms
I have seen ping times as low as 40 ms but I'm sure location is affecting things here.
By using large ping packets (1000 bytes) we get to see if packetloss is introduced when the link is actually being used :
Ping statistics for 196.31.17.162:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 159ms, Maximum = 560ms, Average = 208ms
Still looking good.
The SRT is my final test for this session:
C:\wget>wget http://tucows.is.co.za/files4/DCPlusPlus-0.241.exe
--11:52:36-- http://tucows.is.co.za:80/files4/DCPlusPlus-0.241.exe
=> `DCPlusPlus-0.241.exe'
Connecting to tucows.is.co.za:80... connected!
HTTP request sent, awaiting response... 200 OK
Length: 2,044,011 [application/octet-stream]
11:53:08 (64.39 KB/s) - `DCPlusPlus-0.241.exe' saved [2044011/2044011]
Not quite the throughput they said I'd be capable of but with a varying signal strength between 50-70% I'm not unhappy.
Hope to get my latency graphing tools etc running on this baby soon (under linux)..
<hr noshade size="1"><font size="1"><div align="right">8:00 Thursday 26 August 2004 is <font color="red">D-Day</font id="red">....
<s> 16 17 18 19</s> 20 <font color="green">21 20</font id="green"> 23 24 25 <font color="red"><b>26</b></font id="red">
</div id="right"></font id="size1">
I've been asked a few times on performance metrics of the iBurst system. While I'm not sure how this will compare to the rollout version I thought I'd give some quick feedback on ping times;packet loss and throughput.
ping times are directly related to signal quality. The higher the quality the better the ping times. This may also have to do with the error correction mechanisms of the gear.
Ping statistics for 196.31.17.162:
Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 69ms, Maximum = 139ms, Average = 75ms
I have seen ping times as low as 40 ms but I'm sure location is affecting things here.
By using large ping packets (1000 bytes) we get to see if packetloss is introduced when the link is actually being used :
Ping statistics for 196.31.17.162:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 159ms, Maximum = 560ms, Average = 208ms
Still looking good.
The SRT is my final test for this session:
C:\wget>wget http://tucows.is.co.za/files4/DCPlusPlus-0.241.exe
--11:52:36-- http://tucows.is.co.za:80/files4/DCPlusPlus-0.241.exe
=> `DCPlusPlus-0.241.exe'
Connecting to tucows.is.co.za:80... connected!
HTTP request sent, awaiting response... 200 OK
Length: 2,044,011 [application/octet-stream]
11:53:08 (64.39 KB/s) - `DCPlusPlus-0.241.exe' saved [2044011/2044011]
Not quite the throughput they said I'd be capable of but with a varying signal strength between 50-70% I'm not unhappy.
Hope to get my latency graphing tools etc running on this baby soon (under linux)..
<hr noshade size="1"><font size="1"><div align="right">8:00 Thursday 26 August 2004 is <font color="red">D-Day</font id="red">....
<s> 16 17 18 19</s> 20 <font color="green">21 20</font id="green"> 23 24 25 <font color="red"><b>26</b></font id="red">
</div id="right"></font id="size1">