Statistics

O

OKiDOKi

Member
Joined
Aug 19, 2003
Messages
11
Reaction score
0
Location
South Africa.
Here is some tests we did on #myadsl

OKiDOKi (Me) Capped ADSL
Tharaxis 56k Dailup

---------------------------------------------------------------
<OKiDOKi> first atlantic.owo.com
<OKiDOKi> Packets: Sent = 4, Received = 1, Lost = 3 (75% loss)
<OKiDOKi> Minimum = 390ms, Maximum = 390ms, Average = 390ms
<OKiDOKi> now www.google.com
<OKiDOKi> Packets: Sent = 4, Received = 2, Lost = 2 (50% loss)
<OKiDOKi> Minimum = 660ms, Maximum = 660ms, Average = 660ms
<Tharaxis> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
<Tharaxis> Approximate round trip times in milli-seconds:
<Tharaxis> Minimum = 731ms, Maximum = 767ms, Average = 753ms
<Tharaxis> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
<Tharaxis> Approximate round trip times in milli-seconds:
<Tharaxis> Minimum = 782ms, Maximum = 873ms, Average = 826ms
----------------------------------------------------------------

Anyone wanna add uncapped stats please?
 
uncapped to google:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 515ms, Maximum = 642ms, Average = 574ms

This is not much better than when I was capped, except, when capped I got 75% packet loss.

But remember, these aren't priority packets. So you will see relatively high latency.
 
Pinging www.google.com [216.239.53.99] with 32 bytes of data:

Reply from 216.239.53.99: bytes=32 time=371ms TTL=44
Reply from 216.239.53.99: bytes=32 time=380ms TTL=44
Reply from 216.239.53.99: bytes=32 time=391ms TTL=44
Reply from 216.239.53.99: bytes=32 time=400ms TTL=44

Ping statistics for 216.239.53.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 371ms, Maximum = 400ms, Average = 385ms
 
I don't want to sound noobish, but how do you guys do those tests in the first place. Do you use a certain program?

Tell me so that i can do it too.
 
hehe,

OK... Click on the renowned "Start" button then "Run", it will bring up a dialog and type in "command" or "cmd".
It will pop up the ducky command line window.
Now type in "ping www.google.com".

BTW if you are capped it should look something like this...

Pinging www.google.com [216.239.53.99] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 216.239.53.99:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

It's a non riant event.
 
Ok

I tried and lost about 50% info.

Incredible how much faster pings you get on local sites than international.
 
To select the text output, click and hold the left mouse button and select all the output text. Release the button, and press [enter].

You can then paste it in a message here by pressing Ctrl+V:

C:\>ping google.com

Pinging google.com [216.239.51.100] with 32 bytes of data:

Reply from 216.239.51.100: bytes=32 time=50ms TTL=49
Reply from 216.239.51.100: bytes=32 time=40ms TTL=49
Reply from 216.239.51.100: bytes=32 time=40ms TTL=49
Reply from 216.239.51.100: bytes=32 time=40ms TTL=49

Ping statistics for 216.239.51.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 50ms, Average = 42ms
 
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>ping www.google.com

Pinging www.google.com [216.239.53.99] with 32 bytes of data:

Reply from 216.239.53.99: bytes=32 time=841ms TTL=48
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 216.239.53.99:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 841ms, Maximum = 841ms, Average = 841ms

did I just hit a cap or do I just have bad copper quality??
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X