RE: TCP reaching to maximum throughput after a long time

On Wed, Apr 13, 2016 at 17:32:29, Neal Cardwell wrote: > Miller; Eric Dumazet; Nandita Dukkipati; open list; Kama, Meirav > Subject: Re: TCP reaching to maximum throughput after a long time > > I like the idea to disable hystart ack-train. > > > Yaniv, can you please re-run

RE: TCP reaching to maximum throughput after a long time

On Wed, Apr 13, 2016 at 17:32:29, Neal Cardwell wrote: > Miller; Eric Dumazet; Nandita Dukkipati; open list; Kama, Meirav > Subject: Re: TCP reaching to maximum throughput after a long time > > I like the idea to disable hystart ack-train. > > > Yaniv, can you please re-run

Re: TCP reaching to maximum throughput after a long time

On Tue, 2016-04-12 at 20:08 -0700, Yuchung Cheng wrote: > based on the prev thread I propose we disable hystart ack-train. It is > brittle under various circumstances. We've disabled that at Google for > years. Right, but because we also use sch_fq packet scheduler and pacing ;)

Re: TCP reaching to maximum throughput after a long time

On Tue, 2016-04-12 at 20:08 -0700, Yuchung Cheng wrote: > based on the prev thread I propose we disable hystart ack-train. It is > brittle under various circumstances. We've disabled that at Google for > years. Right, but because we also use sch_fq packet scheduler and pacing ;)

Re: TCP reaching to maximum throughput after a long time

On Tue, Apr 12, 2016 at 2:40 PM, Ben Greear wrote: > On 04/12/2016 01:29 PM, Eric Dumazet wrote: >> >> On Tue, 2016-04-12 at 13:23 -0700, Ben Greear wrote: >> >>> It worked well enough for years that I didn't even know other algorithms >>> were >>> available. It was

Re: TCP reaching to maximum throughput after a long time

On Tue, Apr 12, 2016 at 2:40 PM, Ben Greear wrote: > On 04/12/2016 01:29 PM, Eric Dumazet wrote: >> >> On Tue, 2016-04-12 at 13:23 -0700, Ben Greear wrote: >> >>> It worked well enough for years that I didn't even know other algorithms >>> were >>> available. It was broken around 4.0 time, and I

Re: TCP reaching to maximum throughput after a long time

On 04/12/2016 01:29 PM, Eric Dumazet wrote: On Tue, 2016-04-12 at 13:23 -0700, Ben Greear wrote: It worked well enough for years that I didn't even know other algorithms were available. It was broken around 4.0 time, and I reported it to the list, and no one seemed to really care enough to do

Re: TCP reaching to maximum throughput after a long time

On 04/12/2016 01:29 PM, Eric Dumazet wrote: On Tue, 2016-04-12 at 13:23 -0700, Ben Greear wrote: It worked well enough for years that I didn't even know other algorithms were available. It was broken around 4.0 time, and I reported it to the list, and no one seemed to really care enough to do

Re: TCP reaching to maximum throughput after a long time

On Tue, 2016-04-12 at 13:23 -0700, Ben Greear wrote: > It worked well enough for years that I didn't even know other algorithms were > available. It was broken around 4.0 time, and I reported it to the list, > and no one seemed to really care enough to do anything about it. I changed > to reno

Re: TCP reaching to maximum throughput after a long time

On Tue, 2016-04-12 at 13:23 -0700, Ben Greear wrote: > It worked well enough for years that I didn't even know other algorithms were > available. It was broken around 4.0 time, and I reported it to the list, > and no one seemed to really care enough to do anything about it. I changed > to reno

Re: TCP reaching to maximum throughput after a long time

On 04/12/2016 01:17 PM, Eric Dumazet wrote: On Tue, 2016-04-12 at 13:11 -0700, Ben Greear wrote: On 04/12/2016 12:31 PM, Machani, Yaniv wrote: On Tue, Apr 12, 2016 at 18:04:52, Ben Greear wrote: On 04/12/2016 07:52 AM, Eric Dumazet wrote: On Tue, 2016-04-12 at 12:17 +, Machani, Yaniv

Re: TCP reaching to maximum throughput after a long time

On 04/12/2016 01:17 PM, Eric Dumazet wrote: On Tue, 2016-04-12 at 13:11 -0700, Ben Greear wrote: On 04/12/2016 12:31 PM, Machani, Yaniv wrote: On Tue, Apr 12, 2016 at 18:04:52, Ben Greear wrote: On 04/12/2016 07:52 AM, Eric Dumazet wrote: On Tue, 2016-04-12 at 12:17 +, Machani, Yaniv

Re: TCP reaching to maximum throughput after a long time

On Tue, 2016-04-12 at 13:11 -0700, Ben Greear wrote: > On 04/12/2016 12:31 PM, Machani, Yaniv wrote: > > On Tue, Apr 12, 2016 at 18:04:52, Ben Greear wrote: > >> On 04/12/2016 07:52 AM, Eric Dumazet wrote: > >>> On Tue, 2016-04-12 at 12:17 +, Machani, Yaniv wrote: > > >> > >> If you are

Re: TCP reaching to maximum throughput after a long time

On Tue, 2016-04-12 at 13:11 -0700, Ben Greear wrote: > On 04/12/2016 12:31 PM, Machani, Yaniv wrote: > > On Tue, Apr 12, 2016 at 18:04:52, Ben Greear wrote: > >> On 04/12/2016 07:52 AM, Eric Dumazet wrote: > >>> On Tue, 2016-04-12 at 12:17 +, Machani, Yaniv wrote: > > >> > >> If you are

Re: TCP reaching to maximum throughput after a long time

On 04/12/2016 12:31 PM, Machani, Yaniv wrote: On Tue, Apr 12, 2016 at 18:04:52, Ben Greear wrote: On 04/12/2016 07:52 AM, Eric Dumazet wrote: On Tue, 2016-04-12 at 12:17 +, Machani, Yaniv wrote: If you are using 'Cubic' TCP congestion control, then please try something different. It

Re: TCP reaching to maximum throughput after a long time

On 04/12/2016 12:31 PM, Machani, Yaniv wrote: On Tue, Apr 12, 2016 at 18:04:52, Ben Greear wrote: On 04/12/2016 07:52 AM, Eric Dumazet wrote: On Tue, 2016-04-12 at 12:17 +, Machani, Yaniv wrote: If you are using 'Cubic' TCP congestion control, then please try something different. It

RE: TCP reaching to maximum throughput after a long time

On Tue, Apr 12, 2016 at 18:04:52, Ben Greear wrote: > On 04/12/2016 07:52 AM, Eric Dumazet wrote: > > On Tue, 2016-04-12 at 12:17 +, Machani, Yaniv wrote: >>> > > If you are using 'Cubic' TCP congestion control, then please try > something different. > It was broken last I checked, at least

RE: TCP reaching to maximum throughput after a long time

On Tue, Apr 12, 2016 at 18:04:52, Ben Greear wrote: > On 04/12/2016 07:52 AM, Eric Dumazet wrote: > > On Tue, 2016-04-12 at 12:17 +, Machani, Yaniv wrote: >>> > > If you are using 'Cubic' TCP congestion control, then please try > something different. > It was broken last I checked, at least

Re: TCP reaching to maximum throughput after a long time

On Tue, Apr 12, 2016 at 7:52 AM, Eric Dumazet wrote: > > On Tue, 2016-04-12 at 12:17 +, Machani, Yaniv wrote: > > Hi, > > After updating from Kernel 3.14 to Kernel 4.4 we have seen a TCP > > performance degradation over Wi-Fi. > > In 3.14 kernel, TCP got to its max

Re: TCP reaching to maximum throughput after a long time

On Tue, Apr 12, 2016 at 7:52 AM, Eric Dumazet wrote: > > On Tue, 2016-04-12 at 12:17 +, Machani, Yaniv wrote: > > Hi, > > After updating from Kernel 3.14 to Kernel 4.4 we have seen a TCP > > performance degradation over Wi-Fi. > > In 3.14 kernel, TCP got to its max throughout after less than

Re: TCP reaching to maximum throughput after a long time

On 04/12/2016 07:52 AM, Eric Dumazet wrote: On Tue, 2016-04-12 at 12:17 +, Machani, Yaniv wrote: Hi, After updating from Kernel 3.14 to Kernel 4.4 we have seen a TCP performance degradation over Wi-Fi. In 3.14 kernel, TCP got to its max throughout after less than a second, while in the

Re: TCP reaching to maximum throughput after a long time

On 04/12/2016 07:52 AM, Eric Dumazet wrote: On Tue, 2016-04-12 at 12:17 +, Machani, Yaniv wrote: Hi, After updating from Kernel 3.14 to Kernel 4.4 we have seen a TCP performance degradation over Wi-Fi. In 3.14 kernel, TCP got to its max throughout after less than a second, while in the

Re: TCP reaching to maximum throughput after a long time

On Tue, 2016-04-12 at 12:17 +, Machani, Yaniv wrote: > Hi, > After updating from Kernel 3.14 to Kernel 4.4 we have seen a TCP performance > degradation over Wi-Fi. > In 3.14 kernel, TCP got to its max throughout after less than a second, while > in the 4.4 it is taking ~20-30 seconds. > UDP

Re: TCP reaching to maximum throughput after a long time

On Tue, 2016-04-12 at 12:17 +, Machani, Yaniv wrote: > Hi, > After updating from Kernel 3.14 to Kernel 4.4 we have seen a TCP performance > degradation over Wi-Fi. > In 3.14 kernel, TCP got to its max throughout after less than a second, while > in the 4.4 it is taking ~20-30 seconds. > UDP

TCP reaching to maximum throughput after a long time

Hi, After updating from Kernel 3.14 to Kernel 4.4 we have seen a TCP performance degradation over Wi-Fi. In 3.14 kernel, TCP got to its max throughout after less than a second, while in the 4.4 it is taking ~20-30 seconds. UDP TX/RX and TCP RX performance is as expected. We are using a Beagle

TCP reaching to maximum throughput after a long time

Hi, After updating from Kernel 3.14 to Kernel 4.4 we have seen a TCP performance degradation over Wi-Fi. In 3.14 kernel, TCP got to its max throughout after less than a second, while in the 4.4 it is taking ~20-30 seconds. UDP TX/RX and TCP RX performance is as expected. We are using a Beagle