From: Willy Tarreau <willy@w.ods.org>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: Roberto Nibali <ratz@drugphish.ch>,
willy@w.ods.org, linux-kernel@vger.kernel.org
Subject: Re: hidden interface (ARP) 2.4.20
Date: Sun, 8 Dec 2002 18:01:35 +0100 [thread overview]
Message-ID: <20021208170135.GA354@alpha.home.local> (raw)
In-Reply-To: <20021208170336.5f4deaf1.skraw@ithnet.com>
On Sun, Dec 08, 2002 at 05:03:36PM +0100, Stephan von Krawczynski wrote:
> > Not with a HW LB, and with a SW LB (LVS-NAT) you can very well sustain
> > 20000 NAT'd load balanced connections with 5 minutes of stickyness
> > (persistency) with 1GB RAM and a PIII Tualatin with 512 kb L2 cache. I'm
> > not sure if you meant this when mentioning pain.
>
> I guess he probably meant a _bit_ more. I may add some zeros to your 20000 to
> give you a glimpse of a _standard_ load we are talking about. And you can
> easily do this with the hardware you mentioned _not_ using NAT (of course ;-).
You're right, we have been discussing this privately and agreed we were both
talking about higher numbers ; Robert seems to have a good experience of very
high traffic ;-)
> I guess it would really be a great help if someone did tests like Cons'
> "overall performance" ones for network performance explicitly. Like e.g.
> performance for various packet-sizes of all available protocol types, possibly
> including NAT connections. We have no comparable figures at hand right now, I
> guess.
Why not ?
I've often been doing this to check the reliability of the network layer of
kernels that I distribute. I often use Tux for this, because it can easily
sustain 10k hits/s during months. But Tux is not in mainstream kernel, we have
to use other tools. Since I'm working on a task scheduler, I may soon have the
base to rewrite my injecter and a fake server to do these tests on mainstream
kernels. I think that several tools already exist for this. You can take a look
at the C10K project to find links. I don't have the URL in mind, google is your
friend.
Cheers,
Willy
next prev parent reply other threads:[~2002-12-08 16:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 20:53 hidden interface (ARP) 2.4.20 Bingner Sam J Contractor PACAF CSS/SCHE
2002-12-05 21:42 ` David S. Miller
2002-12-05 22:03 ` Phil Oester
2002-12-05 22:50 ` Roberto Nibali
2002-12-05 23:48 ` Phil Oester
2002-12-05 23:59 ` Roberto Nibali
2002-12-06 6:01 ` Willy Tarreau
2002-12-06 17:52 ` Stephan von Krawczynski
2002-12-07 23:30 ` Roberto Nibali
2002-12-08 16:03 ` Stephan von Krawczynski
2002-12-08 17:01 ` Willy Tarreau [this message]
2002-12-09 11:08 ` Stephan von Krawczynski
2002-12-10 9:42 ` Gilad Ben-Yossef
2002-12-10 10:40 ` Roberto Nibali
2002-12-10 13:09 ` hidden interface (ARP) 2.4.20 / network performance Stephan von Krawczynski
2002-12-10 18:11 ` Roberto Nibali
2002-12-10 23:29 ` Willy TARREAU
2002-12-10 1:22 ` hidden interface (ARP) 2.4.20 Bill Davidsen
2002-12-10 10:40 ` Roberto Nibali
2002-12-10 14:47 ` Bill Davidsen
2002-12-10 18:15 ` Roberto Nibali
2002-12-11 16:15 ` Bill Davidsen
2002-12-12 1:33 ` Bernd Eckenfels
2002-12-05 22:18 ` Martin Josefsson
-- strict thread matches above, loose matches on Subject: below --
2002-12-05 23:57 Bingner Sam J Contractor PACAF CSS/SCHE
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=20021208170135.GA354@alpha.home.local \
--to=willy@w.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ratz@drugphish.ch \
--cc=skraw@ithnet.com \
/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