[186728] in North American Network Operators' Group
Re: Netflix stuffing data on pipe
daemon@ATHENA.MIT.EDU (Mikael Abrahamsson)
Wed Dec 30 08:34:31 2015
X-Original-To: nanog@nanog.org
Date: Wed, 30 Dec 2015 14:34:27 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Matt Hoppes <mhoppes@indigowireless.com>
In-Reply-To: <097CDCC9-79BF-4405-A255-A1120B011F47@indigowireless.com>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Wed, 30 Dec 2015, Matt Hoppes wrote:
> I'm not buffering. Switches have packet buffers. I'm seeing switch
> buffers getting overrun by what appears to be Netflix traffic coming in
> at rates faster than the subscribers throttled speeds.
How big are your buffers (preferrably answer would be in milliseconds)?
What access speeds are you providing?
It's standard behavior for network traffic to sometimes be at higher
speeds than the customer access speeds, the sender only knows about
congestion if there is an increase in RTT or if there is packet loss (or
in case of ECN, EC=1 flag), and the only way to find out is to probe (=run
faster than customer access speed).
--
Mikael Abrahamsson email: swmike@swm.pp.se
