From: Chris Brenton <cbrenton@chrisbrenton.org>
To: Marcin Sura <slacklist@op.pl>
Cc: netfilter <netfilter@lists.netfilter.org>
Subject: Re: OT: Pings phenomen :)
Date: Sun, 29 Aug 2004 05:29:13 -0400 [thread overview]
Message-ID: <1093771753.1659.8.camel@grendel> (raw)
In-Reply-To: <213736141.20040828221628@op.pl>
On Sat, 2004-08-28 at 16:16, Marcin Sura wrote:
>
> I have 512/128 adsl. I wonder why, when I download files at full
> speed, pings to site X are about 2000ms. But when I upload files at
> full speed, pings to X are about 3000 to 5000ms. Can someone explain
> this to me from tcp/ip point of view? ;)
512 is download speed
128 is upload speed
When you are uploading a file you are sucking up bandwidth on the
smallest portion of your link. This means greater congestion than when
doing a download, so the latency on your echo-request packets is higher.
HTH,
Chris
next prev parent reply other threads:[~2004-08-29 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-28 20:16 OT: Pings phenomen :) Marcin Sura
2004-08-28 17:49 ` Jason Clark
2004-08-28 20:27 ` Nick Taylor
2004-08-29 9:29 ` Chris Brenton [this message]
2004-08-29 16:58 ` Jose Maria Lopez
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=1093771753.1659.8.camel@grendel \
--to=cbrenton@chrisbrenton.org \
--cc=netfilter@lists.netfilter.org \
--cc=slacklist@op.pl \
/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