All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Eric Dumazet <edumazet@google.com>
Cc: Feng Tang <feng.tang@intel.com>,
	kernel test robot <rong.a.chen@intel.com>,
	"David S. Miller" <davem@davemloft.net>,
	Yue Cao <ycao009@ucr.edu>, LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	lkp@lists.01.org
Subject: Re: [LKP] [net] 19f92a030c: apachebench.requests_per_second -37.9% regression
Date: Wed, 13 Nov 2019 18:21:02 +0100	[thread overview]
Message-ID: <20191113172102.GA23306@1wt.eu> (raw)
In-Reply-To: <CANn89iJejNcvARpGR01seeuxV7JViMengX_nqdDV7cfyaisQpQ@mail.gmail.com>

On Wed, Nov 13, 2019 at 08:46:00AM -0800, Eric Dumazet wrote:
> We have been using 4096 at Google for about 5 years, and Google is still
> alive.

Same for most haproxy users, changing from the default 128 to several
thousands always fixes their initial performance problems. There really
must be something else in this test, or it depends on a strange corner
case that's triggered by the increase, but that sounds odd.

Regards,
Willy

      reply	other threads:[~2019-11-13 17:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08  8:35 [net] 19f92a030c: apachebench.requests_per_second -37.9% regression kernel test robot
2019-11-08  8:35 ` kernel test robot
2019-11-13 10:35 ` [LKP] " Feng Tang
2019-11-13 10:35   ` Feng Tang
2019-11-13 14:33   ` [LKP] " Eric Dumazet
2019-11-13 14:33     ` Eric Dumazet
2019-11-13 16:12     ` [LKP] " Feng Tang
2019-11-13 16:12       ` Feng Tang
2019-11-13 16:46       ` Eric Dumazet
2019-11-13 17:21         ` Willy Tarreau [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191113172102.GA23306@1wt.eu \
    --to=w@1wt.eu \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=feng.tang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@lists.01.org \
    --cc=rong.a.chen@intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=ycao009@ucr.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.