Re: bandwidth for bkbits.net (good news)

Jamie Lokier
2003-09-01T00:18:35Z

Andrea Arcangeli wrote:
> On Sun, Aug 31, 2003 at 03:56:39PM -0700, Larry McVoy wrote:
> > Yet you keep insisting it will work. Why? What is the theory that says
> > you can keep the other end of the T1 line from being congested when you
> > don't have control over that router? And that router has several 100Mbit
>
> it's absolutely trivial, your end only needs to drop 99% of your
> outgoing acks and their incoming packets for every connection but voip
> while you are at the phone, you won't kill the connections but everybody
> but your voip will work. the exponential backoff and sstrash on the
> other and will rate limit everything immediatly.

Let's work it out. We assume 99% means drop virtually everything:

Every 19 seconds on average, 24x7, a new HTTP connection.

Rate is not uniform throughout the day. Let's take a wild guess and
say it is 10 times higher at peak times.

That's one connection every 1.9 seconds.

Let's assume you drop 99% of outgoing ACKs.

Then all connecting remote clients will retry their SYNs until they
get a connection or a timeout. Default tcp_syn_retries (assuming Linux
clients) is 5.

That's one SYN every 0.38 seconds. -> bad but not awful.

Plus existing connections. Let's pretend each connection take 100 seconds.

That's 100/1.9 or 52 concurrent connections, roughly.

Each of those will retry with an ACK if it has any pending ACK or data.

When you start using the phone, that's 100 ACKs total,
approximately, with exponential backoff. --> bad but not awful.

These calculations are horrendously inaccurate, but should be ok
within a couple of orders of magnitude.

So, near-total annihilation of bkbits.net when Larry or any of his
team are on the phone should work. You can either integrate the phone
system with netfilter so it is automatic when a customer calls.
Trivial ;) Or disable bkbits.net during Larry's working day. ;)

-- Jamie