linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Samuel <samuel@bcgreen.com>
To: Luca Ferrari <fluca1978@infinito.it>
Cc: linux-admin@vger.kernel.org
Subject: Re: how reliable is ping?
Date: Mon, 13 Dec 2004 14:28:32 -0800	[thread overview]
Message-ID: <41BE1790.7020204@bcgreen.com> (raw)
In-Reply-To: <200412061019.19099.fluca1978@infinito.it>

Luca Ferrari wrote:
> Hi,
> in my company we installed a new DSL line, supposed to be faster than the 
> previous one. And in fact it seems to be, in interactive use, but if I use 
> ping to test connectivity against the old line I can see higher times. So my 
> questions is: why does ping show high times and then the line goes faster? Is 
> ping reliable enough to test network speed, or should I use another tool? (at 
> last, a chrono and a file transfer!)

There are many things that test network reactivity, and ping
only checks one or two of them.

Ping times only indicate how long it takes a packet to make it
from my box to yours, and back. The command is mostly intended
to just check to make sure that the machine is up.

  Note that some routers give ping packets lower priority, aince
they're (almost) never sending any real data.

Cable connections often have a beter intrinsic bandwidth
availability but they're more sporadic because they're shared
among some number of users in your neighborhood -- in other
words, you might get really good bandwith at 4AM and
sorse-than-modem bandwidth at 7PM.

In truth, ping times don't predict bandwidth. If you have two
machines at the same colo site, one which is bandwidth limited
to 18Kb/s and the other with an unlimited 10Mbit connection,
they may both give you the same ping times, but vastly different
download speeds.

Similarly, a modem user in your city may give a slightly better
ping time than a well-connect box across the country (or even
across the ocean), but still give far worse downloads.

Snother difference between cable and DSL is that, because
DSL is shared, the ping times are less *predictable*.  If
you're playing counterstrike, very low average latency with
short bursts of high-latency can be far more bothersome than
a slightly higher average latency that is more stable.


-- 
Stephen Samuel +1(604)876-0426                samuel@bcgreen.com
		   http://www.bcgreen.com/~samuel/
    Powerful committed communication. Transformation touching
      the jewel within each person and bringing it to light.

      parent reply	other threads:[~2004-12-13 22:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-06  9:19 how reliable is ping? Luca Ferrari
2004-12-06  9:29 ` Helge Pettersen
2004-12-06  9:38   ` Adrian C.
2004-12-06 10:06     ` Marcel Gschwandl
2004-12-06  9:55       ` urgrue
2004-12-06 11:10         ` Alexander Economou
2004-12-06 20:10           ` Matías López Bergero
2004-12-08  0:37       ` Jeff Woods
2004-12-13 22:28 ` Stephen Samuel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41BE1790.7020204@bcgreen.com \
    --to=samuel@bcgreen.com \
    --cc=fluca1978@infinito.it \
    --cc=linux-admin@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).