Re: Netflix stuffing data on pipe

2016-01-04 Thread Owen DeLong
The most obvious things would be to make feedback faster… Implement congestion controls further up stream with reduced buffering throughout the network, selective technologies like WRED, etc. As RS said, sure, but all come at a cost either in performance, equipment, support, or some combination

Re: Netflix stuffing data on pipe

2016-01-04 Thread Rob Seastrom
I haven't done packet dumps to verify the behavior (too busy catching up on holiday email) but I can't help but wonder if IW10 (on by default in FreeBSD 10 which I believe might be what Netflix has underneath) is causing this problem, and that maybe a more gentle CWND ramp-up (or otherwise tweak

Re: Netflix stuffing data on pipe

2016-01-04 Thread Pete Mundy
Very succiently put, Owen! I concur. Is anything the ISP could avoid to alleviate this occurrence, or is it entirely a 'server-side' issue to resolve? Pete > On 4/01/2016, at 8:42 pm, Owen DeLong wrote: > > As I understand it, the problem being discussed is an oscillation that is > creat

Re: Netflix stuffing data on pipe

2016-01-03 Thread Owen DeLong
As I understand it, the problem being discussed is an oscillation that is created when the reaction occurs faster than the feedback resulting in a series of dynamically increasing overcompensations. Owen > On Jan 3, 2016, at 21:26 , Justin Wilson wrote: > > Netflix is streaming video. It wil

Re: Netflix stuffing data on pipe

2016-01-03 Thread Justin Wilson
Netflix is streaming video. It will try to do the best data rate it can. If the connection can handle 4 megs a second it is going to try and do 4 megs a second. If the network can’t handle it then Netflix will back off and adapt to try and fit. Keep in mind, at least last I knew, a full HD

Re: Netflix stuffing data on pipe

2015-12-31 Thread Evelio Vila
It is actually buffer-based, as it picks the video rate as a function of the current buffer occupancy. See here http://yuba.stanford.edu/~nickm/papers/sigcomm2014-video.pdf -- evelio On Tue, Dec 29, 2015 at 6:56 PM, Matt Hoppes wrote: > Has anyone else observed Netflix sessions attempting to c

Re: Netflix stuffing data on pipe

2015-12-30 Thread Ca By
On Tuesday, December 29, 2015, Josh Reynolds wrote: > Adaptive bandwidth detection. Yes, ABR video attempts to fill the entire channel This has been problematic as peak edge speeds have increased and pushed the statistical multplexing logic / plans. There is also buffer bloat issues that exa

Re: Netflix stuffing data on pipe

2015-12-30 Thread Mike Hammett
-ix.com - Original Message - From: "Josh Reynolds" To: "Matt Hoppes" Cc: "NANOG" Sent: Tuesday, December 29, 2015 9:10:51 PM Subject: Re: Netflix stuffing data on pipe Adaptive bandwidth detection. On Dec 29, 2015 8:59 PM, "Matt Hoppes&qu

Re: Netflix stuffing data on pipe

2015-12-30 Thread Mikael Abrahamsson
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 mi

Re: Netflix stuffing data on pipe

2015-12-30 Thread Roland Dobbins
On 30 Dec 2015, at 19:42, Matt Hoppes wrote: I'm seeing switch buffers getting overrun by what appears to be Netflix traffic coming in at rates faster than the subscribers throttled speeds. By what mechanism is the throttling accomplished? QoS on routers, or some kind of middlebox, or . . .

Re: Netflix stuffing data on pipe

2015-12-30 Thread Matt Hoppes
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. > On Dec 30, 2015, at 02:59, Hugo Slabbert wrote: > >> On Tue 2015-Dec-29 21:17:51 -0600, Josh Reyn

Re: Netflix stuffing data on pipe

2015-12-30 Thread Josh Reynolds
It's a long and ugly story... 1Gbps FD feeds -> switch -> 100Mbps FD radio port -> fluctuating PHY rate Half Duplex wireless link/CPE (shaped here). Netflix is microbusting, and its really nasty on his kind of network, especially with the shaping being toward the end of his network. On Dec 30, 20

Re: Netflix stuffing data on pipe

2015-12-30 Thread Hugo Slabbert
On Tue 2015-Dec-29 21:17:51 -0600, Josh Reynolds wrote: The second part. Fixed wireless is not even on their radar. On Dec 29, 2015 9:16 PM, "Matt Hoppes" wrote: So they are trying to stuff every last bit as an end device modulates up and down? Or are you saying that's how they determine if

Re: Netflix stuffing data on pipe

2015-12-29 Thread Josh Reynolds
The second part. Fixed wireless is not even on their radar. On Dec 29, 2015 9:16 PM, "Matt Hoppes" wrote: > So they are trying to stuff every last bit as an end device modulates up > and down? > > Or are you saying that's how they determine if they can scale up the > resolution "because there is

Re: Netflix stuffing data on pipe

2015-12-29 Thread Matt Hoppes
So they are trying to stuff every last bit as an end device modulates up and down? Or are you saying that's how they determine if they can scale up the resolution "because there is more throughout available now". > On Dec 29, 2015, at 22:10, Josh Reynolds wrote: > > Adaptive bandwidth detect

Re: Netflix stuffing data on pipe

2015-12-29 Thread Josh Reynolds
Adaptive bandwidth detection. On Dec 29, 2015 8:59 PM, "Matt Hoppes" wrote: > Has anyone else observed Netflix sessions attempting to come into customer > CPE devices at well in excess of the customers throttled plan? > > I'm not talking error retries on the line. I'm talking like two to three >

Netflix stuffing data on pipe

2015-12-29 Thread Matt Hoppes
Has anyone else observed Netflix sessions attempting to come into customer CPE devices at well in excess of the customers throttled plan? I'm not talking error retries on the line. I'm talking like two to three times in excess of what the customers CPE device can handle. I'm observing massive