From: Andrea Arcangeli <aarcange@redhat.com>
To: lkp@lists.01.org
Subject: Re: [sched/fair] 69bc1b14c3: netperf.Throughput_Mbps -36.9% regression
Date: Tue, 25 May 2021 17:16:26 -0400 [thread overview]
Message-ID: <YK1pKv4Gna2EEFSd@redhat.com> (raw)
In-Reply-To: <49d2cb2c-8a6f-f8a5-af07-b9be2d59f73e@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]
On Mon, May 24, 2021 at 10:46:54AM +0800, Xing, Zhengjun wrote:
> The command we used :
> netperf -4 -H 127.0.0.1 -t TCP_SENDFILE -c -C -l 300 -- -m 5K &
>
> It runs 300 s, but your test case only runs 10 s, I think you can try
> to test more long time.
I don't know what was going on and why I couldn't reproduce. Later I
managed to reproduce something erratic with stress-ng sockabuse, I
didn't manage to reproduce with netperf but I'm hopeful it's the same
thing that regresses various workloads on the same large CPU systems.
Anyway I should have fixed it, if you can test the new version I'd be
interested.
Also I switched the default HEAD branch to main, I hope that won't
confuse your automation that may have been attached to "master".
https://git.kernel.org/pub/scm/linux/kernel/git/andrea/aa.git/commit/?id=1a49bc1fe57152d27743effc64c0e2899939793d
With an Intel 112 threads, 28 cores per socket and 2 sockets (2 NUMA
nodes) this gave me a 17% boost in sockabuse ops/sec.
prev parent reply other threads:[~2021-05-25 21:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 7:17 [sched/fair] 69bc1b14c3: netperf.Throughput_Mbps -36.9% regression kernel test robot
2021-05-20 18:47 ` Andrea Arcangeli
2021-05-21 7:20 ` Xing, Zhengjun
2021-05-21 23:45 ` Andrea Arcangeli
2021-05-24 2:46 ` Xing, Zhengjun
2021-05-25 21:16 ` Andrea Arcangeli [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=YK1pKv4Gna2EEFSd@redhat.com \
--to=aarcange@redhat.com \
--cc=lkp@lists.01.org \
/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.