From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Willy Tarreau <willy@w.ods.org>
Cc: Ragnar Kj?rstad <kernel@ragnark.vestdata.no>,
linux-kernel@vger.kernel.org, lftp@uniyar.ac.ru,
lftp-devel@uniyar.ac.ru, apiszcz@mitre.org,
ext2-devel@lists.sourceforge.net
Subject: Re: Nasty ext2fs bug!
Date: Thu, 01 Aug 2002 15:21:24 -0400 [thread overview]
Message-ID: <3D498A34.A1A914E4@lucidpixels.com> (raw)
In-Reply-To: 20020801183825.GA20265@alpha.home.local
My ISP = Adelphia.
The area in which I live in has many problems, simply check:
http://www.dslreports.com/forum/adelphia
The post with 700+ threads is where I am.
Basically, each thread from their service only gives you 10-20KB/s.
To get any decent speed while downloading, you must download in parallel or
split the file up.
Willy Tarreau wrote:
> On Thu, Aug 01, 2002 at 08:27:18PM +0200, Ragnar Kj?rstad wrote:
> > On Thu, Aug 01, 2002 at 11:48:56AM -0600, Andreas Dilger wrote:
> > > I find it hard to believe that this would actually make a huge
> > > difference, except in the case where the source is throttling bandwidth
> > > on a per-connection basis. Either your network is saturated by the
> > > transfer, or some point in between is saturated. I could be wrong, of
> > > course, and it would be interesting to hear the reasoning behind the
> > > speedup.
> > If some link is saturated with 1000 connections, you will get 1% of the
> > bandwith instead of 0.1% if you use 10 concurrent connections. right?
>
> wrong, you'll get 1% of the connections instead of 0.1%. So you'll be
> more responsible for the saturation of some active equipments which
> are sensible to connections, but this has nothing to do with the
> bandwidth, nor the link.
>
> It may be usefull only if you have a very high latency and a small
> TCP window, I think.
>
> Cheers,
> Willy
next prev parent reply other threads:[~2002-08-01 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 16:54 Nasty ext2fs bug! jpiszcz
2002-08-01 17:48 ` Andreas Dilger
2002-08-01 18:27 ` Ragnar Kjørstad
2002-08-01 18:38 ` Willy Tarreau
2002-08-01 19:21 ` Justin Piszcz [this message]
2002-08-01 19:20 ` Justin Piszcz
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=3D498A34.A1A914E4@lucidpixels.com \
--to=jpiszcz@lucidpixels.com \
--cc=apiszcz@mitre.org \
--cc=ext2-devel@lists.sourceforge.net \
--cc=kernel@ragnark.vestdata.no \
--cc=lftp-devel@uniyar.ac.ru \
--cc=lftp@uniyar.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@w.ods.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