From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: "Ragnar Kjørstad" <kernel@ragnark.vestdata.no>
Cc: 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:20:01 -0400 [thread overview]
Message-ID: <3D4989E1.90B2CC78@lucidpixels.com> (raw)
In-Reply-To: 20020801202718.S20768@vestdata.no
The remote link is an un-utilized T3.
The downlink is a 3MBIT cable modem.
Ragnar Kjørstad wrote:
> On Thu, Aug 01, 2002 at 11:48:56AM -0600, Andreas Dilger wrote:
> > > Problem: The pget -n feature of lftp is very nice if you want to maximize
> > > your download bandwidth, however, if getting a large file, such
> > > as the one I am getting, once the file is successfully
> > > retrived, transferring it to another HDD or FTPing it to another
> > > computer is very slow (800KB-1600KB/s).
> >
> > 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?
>
> --
> Ragnar Kjørstad
prev parent reply other threads:[~2002-08-01 19:21 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
2002-08-01 19:20 ` Justin Piszcz [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=3D4989E1.90B2CC78@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 \
/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