[184706] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Google's peering, GGC, and congestion management

daemon@ATHENA.MIT.EDU (Baldur Norddahl)
Thu Oct 15 15:50:36 2015

X-Original-To: nanog@nanog.org
In-Reply-To: <40EAB231-AC6E-4C79-B408-99F3517C540F@ianai.net>
Date: Thu, 15 Oct 2015 21:50:30 +0200
From: Baldur Norddahl <baldur.norddahl@gmail.com>
To: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org

On 15 October 2015 at 16:35, Patrick W. Gilmore <patrick@ianai.net> wrote:

> The 100% number is silly. My guess? They=E2=80=99re at 98%.
>
> That is easily do-able because all the traffic is coming from them.
> Coordinate the HTTPd on each of the servers to serve traffic at X bytes p=
er
> second, ensure you have enough buffer in the switches for micro-bursts,
> check the NICs for silliness such as jitter, and so on. It is non-trivial=
,
> but definitely solvable.
>

You would not need to control the servers to do this. All you need is the
usual hash function of src+dst ip+port to map sessions into buckets and
then dynamically compute how big a fraction of the buckets to route through
a different path.

A bit surprising that this is not a standard feature on routers.

Regards,

Baldur

home help back first fref pref prev next nref lref last post