From: Andrea Arcangeli <andrea@suse.de>
To: Jamie Lokier <jamie@shareable.org>
Cc: Larry McVoy <lm@work.bitmover.com>, Larry McVoy <lm@bitmover.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Pascal Schmidt <der.eremit@email.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: bandwidth for bkbits.net (good news)
Date: Mon, 1 Sep 2003 03:10:55 +0200 [thread overview]
Message-ID: <20030901011055.GE11503@dualathlon.random> (raw)
In-Reply-To: <20030901005041.GC31531@mail.jlokier.co.uk>
On Mon, Sep 01, 2003 at 01:50:41AM +0100, Jamie Lokier wrote:
> Andrea Arcangeli wrote:
> > Depending on the connect/sec of the http server (not bkbits, for the
> > largest part of the conversation I couldn't know about the http server,
> > Larry only mentioned the bkbits.net clone until recently), the
> > "reservation" margin will have to change: the less connect/sec the
> > smaller margin Larry will need to reserve, the more connect/sec the
> > bigger marging will be necessary.
>
> Hi Andrea,
>
> Above a certain connection rate, no amount of margin is enough. The
> connections are a SYN flood.
>
> You need to take into account the peak rate, which varies from second
> to second, due to simple statistics plus the tendency of the net to
> make traffic burstier than it started.
>
> Above a certain number of packets/sec, competing VoIP traffic degrades
> - a little added latency is equivalent to dropping with VoIP. That
> translates to dropouts in the audio. Acceptable for hackers talking
> over a flakey line, but not corporate telephony.
>
> At Larry's server, inbound connection rate resembles a low-level SYN
> flood, which is enough to poke holes in VoIP latency.
Yes. if you check my very first email in this thread, you will see I
said "it has to work, unless you're under syn-flood ;)".
this is obvious, I'm not arguing about that. From Larry's description of
the problem it couldn't be a syn flood, but it was a bkbits.net clone
thing or checkout or whatever non syn intensive.
now apparently bkbits.net has nothing to do with it, and it's all about
the http server. Then of course the syn overhead may become noticeable
but things have changed totally from the original description of the
problem (the bkbits.net clone thing).
however keep in mind you will somehow throttle the number of syns too,
unless every single syn arrives to the webserver from a different user
(unlikely).
Andrea
next prev parent reply other threads:[~2003-09-01 1:10 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <q2SH.AA.3@gated-at.bofh.it>
[not found] ` <qfwI.15D.27@gated-at.bofh.it>
[not found] ` <qgCn.2y4.11@gated-at.bofh.it>
2003-08-30 22:58 ` bandwidth for bkbits.net (good news) Pascal Schmidt
2003-08-30 23:07 ` Larry McVoy
2003-08-31 1:05 ` Pascal Schmidt
2003-08-31 1:39 ` Andrea Arcangeli
2003-08-31 2:18 ` Jeff Sipek
2003-08-31 2:42 ` Andrea Arcangeli
2003-08-31 2:56 ` Larry McVoy
2003-08-31 13:15 ` Alan Cox
2003-08-31 14:45 ` Andrea Arcangeli
2003-08-31 15:31 ` Alan Cox
2003-08-31 15:43 ` Jörn Engel
2003-08-31 15:50 ` Andrea Arcangeli
2003-08-31 17:06 ` Florian Weimer
2003-08-31 21:21 ` Larry McVoy
2003-09-02 7:06 ` Henning P. Schmiedehausen
2003-09-05 8:10 ` Florian Weimer
2003-09-05 15:35 ` Henning Schmiedehausen
2003-09-05 15:50 ` Florian Weimer
2003-09-05 16:10 ` P
2003-09-05 16:43 ` Ricky Beam
2003-09-07 11:55 ` Henning Schmiedehausen
2003-09-07 18:41 ` Ricky Beam
2003-09-08 8:57 ` [COMPLETELY OFF-TOPIC] " Henning Schmiedehausen
2003-09-02 21:52 ` Ricky Beam
2003-09-05 8:16 ` Florian Weimer
2003-08-31 15:44 ` Andrea Arcangeli
2003-08-31 16:22 ` Larry McVoy
2003-08-31 16:33 ` Andrea Arcangeli
2003-08-31 16:48 ` Larry McVoy
2003-08-31 17:06 ` Andrea Arcangeli
2003-08-31 21:18 ` Larry McVoy
2003-08-31 22:49 ` Andrea Arcangeli
2003-08-31 22:52 ` Alan Cox
2003-08-31 22:58 ` Larry McVoy
2003-08-31 23:02 ` Andrea Arcangeli
2003-08-31 23:07 ` Larry McVoy
2003-08-31 23:22 ` Andrea Arcangeli
2003-09-01 0:12 ` Larry McVoy
2003-09-01 0:19 ` Jamie Lokier
2003-09-01 0:33 ` Larry McVoy
2003-09-01 11:43 ` Alan Cox
2003-09-01 16:13 ` Andrea Arcangeli
2003-09-01 16:24 ` Larry McVoy
2003-09-01 16:28 ` Alan Cox
2003-09-01 16:38 ` Andrea Arcangeli
2003-08-31 23:39 ` Roman Zippel
2003-09-01 0:09 ` Larry McVoy
2003-09-01 0:20 ` Larry McVoy
2003-08-31 22:56 ` Larry McVoy
2003-08-31 23:13 ` Andrea Arcangeli
2003-09-01 0:18 ` Jamie Lokier
2003-09-01 0:25 ` Larry McVoy
2003-09-01 0:28 ` Andrea Arcangeli
2003-09-01 0:50 ` Jamie Lokier
2003-09-01 1:10 ` Andrea Arcangeli [this message]
2003-09-01 1:33 ` Larry McVoy
2003-09-02 7:11 ` Henning P. Schmiedehausen
2003-09-02 7:01 ` Henning P. Schmiedehausen
2003-08-31 16:23 ` Larry McVoy
2003-08-31 16:36 ` Andrea Arcangeli
2003-08-31 15:38 ` Jörn Engel
2003-09-02 6:55 ` Henning P. Schmiedehausen
2003-08-31 13:47 ` Pascal Schmidt
2003-08-31 14:51 ` Andrea Arcangeli
2003-09-02 6:53 ` Henning P. Schmiedehausen
2003-08-31 6:30 ` Jörn Engel
[not found] <qn1b.2Pr.29@gated-at.bofh.it>
[not found] ` <qoTh.5mt.11@gated-at.bofh.it>
[not found] ` <rdje.1sH.11@gated-at.bofh.it>
2003-09-02 17:49 ` Pascal Schmidt
2003-08-30 1:29 Larry McVoy
2003-08-30 15:03 ` Larry McVoy
2003-08-30 16:10 ` Jörn Engel
2003-08-31 10:13 ` Toon van der Pas
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=20030901011055.GE11503@dualathlon.random \
--to=andrea@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=der.eremit@email.de \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=lm@work.bitmover.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