public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Richard Moser <nigelenki@comcast.net>
To: Redeeman <lkml@metanurb.dk>
Cc: Erik Mouw <erik@harddisk-recovery.com>,
	LKML Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: quite big breakthrough in the BAD network performance, which mm6 did not fix
Date: Tue, 06 Jul 2004 16:08:31 -0400	[thread overview]
Message-ID: <40EB06BF.208@comcast.net> (raw)
In-Reply-To: <1089128977.10626.11.camel@localhost>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Please follow these instructions:

1.  STFU
2.  Log in as root
3.  emerge apache
4.  Set up a local web server with a large file on it
5.  wget -c the file over your network with each kernel, from another
computer on the local network.

Erik's said several times now to use a local server.  He's right.
You're not.  Probability is against him; but you're still in the box
with schrodinger's cat, so you can't give any sort of guarantee either.
~ His method *does* give a controlled experiment which supplies said
guarantee.

Redeeman wrote:
| On Tue, 2004-07-06 at 15:53 +0200, Erik Mouw wrote:
|
|>On Tue, Jul 06, 2004 at 03:25:30PM +0200, Redeeman wrote:
|>
|>>i am aware of this, however, what i use to benchmark is kernel.org, as i
|>>can see they have alot bandwith free.
|>>if i use kernel.org http i get 50kb/s, if i use ftp, i can easily fetch
|>>with 200kb/s
|>
|>That could be easily explained by the fact that the www.kernel.org ftp
|>and http services are handled by different programs (vsftpd vs.
|>Apache).
|
| yeah it could.. however it isnt. because 2.6.5 can easily take 200kb/s
| from kernel.org http, and it sound strange too, that with 2.6.7 ALL http
| adresses only give 50kb/s, and with 2.6.5 it gives 200 :>
|
|>
|>Erik
|>
|
|
| -
| To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
| the body of a message to majordomo@vger.kernel.org
| More majordomo info at  http://vger.kernel.org/majordomo-info.html
| Please read the FAQ at  http://www.tux.org/lkml/
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFA6wa9hDd4aOud5P8RAm1/AJ4i+9BY9x00QaRZKbB/jBSCV9AbHgCdG7bj
23bKs8ptiLOA32B816Y13vk=
=1oBo
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2004-07-06 20:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-05 23:38 quite big breakthrough in the BAD network performance, which mm6 did not fix Redeeman
2004-07-06  0:54 ` Matt Heler
2004-07-06 13:25   ` Redeeman
2004-07-06 13:53     ` Erik Mouw
2004-07-06 15:49       ` Redeeman
2004-07-06 18:46         ` Matt Heler
2004-07-06 20:08         ` John Richard Moser [this message]
2004-07-06 20:20           ` John Richard Moser
2004-07-06 19:30     ` Horst von Brand
2004-07-07  0:42       ` Redeeman
2004-07-07  1:12         ` Matt Heler
2004-07-07  4:46           ` qubes
2004-07-07  5:46           ` Redeeman
2004-07-07  6:31             ` bert hubert
2004-07-07  6:37               ` Redeeman
2004-07-07  8:19                 ` bert hubert
2004-07-07  8:29                   ` Redeeman
2004-07-07  7:45               ` Redeeman

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=40EB06BF.208@comcast.net \
    --to=nigelenki@comcast.net \
    --cc=erik@harddisk-recovery.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@metanurb.dk \
    /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