netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: kernel test robot <oliver.sang@intel.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
	Moshe Kol <moshe.kol@mail.huji.ac.il>,
	Yossi Gilad <yossi.gilad@mail.huji.ac.il>,
	Amit Klein <aksecurity@gmail.com>,
	Eric Dumazet <edumazet@google.com>,
	LKML <linux-kernel@vger.kernel.org>,
	netdev@vger.kernel.org, lkp@lists.01.org, lkp@intel.com,
	ying.huang@intel.com, feng.tang@intel.com,
	zhengjun.xing@linux.intel.com, fengwei.yin@intel.com
Subject: Re: [tcp]  e926147618:  stress-ng.icmp-flood.ops_per_sec -8.7% regression
Date: Wed, 8 Jun 2022 08:48:22 +0200	[thread overview]
Message-ID: <20220608064822.GC7547@1wt.eu> (raw)
In-Reply-To: <20220608060802.GA22428@xsang-OptiPlex-9020>

On Wed, Jun 08, 2022 at 02:08:02PM +0800, kernel test robot wrote:
> 
> 
> Greeting,
> 
> FYI, we noticed a -8.7% regression of stress-ng.icmp-flood.ops_per_sec due to commit:
> 
> 
> commit: e9261476184be1abd486c9434164b2acbe0ed6c2 ("tcp: dynamically allocate the perturb table used by source ports")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> 
> in testcase: stress-ng
> on test machine: 128 threads 2 sockets Intel(R) Xeon(R) Platinum 8358 CPU @ 2.60GHz with 128G memory
> with following parameters:
> 
> 	nr_threads: 100%
> 	testtime: 60s
> 	class: network
> 	test: icmp-flood
> 	cpufreq_governor: performance
> 	ucode: 0xd000331
> 
> 
> 
> 
> If you fix the issue, kindly add following tag
> Reported-by: kernel test robot <oliver.sang@intel.com>
> 
> 
> Details are as below:
> -------------------------------------------------------------------------------------------------->
> 
> 
> To reproduce:
> 
>         git clone https://github.com/intel/lkp-tests.git
>         cd lkp-tests
>         sudo bin/lkp install job.yaml           # job file is attached in this email
>         bin/lkp split-job --compatible job.yaml # generate the yaml file for lkp run
>         sudo bin/lkp run generated-yaml-file
> 
>         # if come across any failure that blocks the test,
>         # please remove ~/.lkp and /lkp dir to run from a clean state.
> 
> =========================================================================================
> class/compiler/cpufreq_governor/kconfig/nr_threads/rootfs/tbox_group/test/testcase/testtime/ucode:
>   network/gcc-11/performance/x86_64-rhel-8.3/100%/debian-10.4-x86_64-20200603.cgz/lkp-icl-2sp6/icmp-flood/stress-ng/60s/0xd000331
> 
> commit: 
>   ca7af04025 ("tcp: add small random increments to the source port")
>   e926147618 ("tcp: dynamically allocate the perturb table used by source ports")
> 
> ca7af0402550f9a0 e9261476184be1abd486c943416 
> ---------------- --------------------------- 
>          %stddev     %change         %stddev
>              \          |                \  
>  5.847e+08            -8.7%  5.337e+08        stress-ng.icmp-flood.ops
>    9745088            -8.7%    8894785        stress-ng.icmp-flood.ops_per_sec
(...)

I don't know much what to think about it, to be honest. We anticipated
a possible very tiny slowdown by moving the table from static to dynamic,
though that was not observed at all during extensive tests on real
hardware. But it was not acceptable to keep too large a table as static
anyway.

>     102391 ±  2%      -8.1%      94064        stress-ng.time.involuntary_context_switches
>       3069 ±  2%      -9.6%       2775 ±  4%  stress-ng.time.percent_of_cpu_this_job_got
>       1857 ±  2%      -9.3%       1685 ±  4%  stress-ng.time.system_time
>      47.67 ±  4%     -20.9%      37.70 ±  5%  stress-ng.time.user_time

Not sure what to think about these variations, nor how they may be related.

Thanks,
Willy

  reply	other threads:[~2022-06-08  7:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08  6:08 [tcp] e926147618: stress-ng.icmp-flood.ops_per_sec -8.7% regression kernel test robot
2022-06-08  6:48 ` Willy Tarreau [this message]
     [not found]   ` <CACi_AuAr70bDB79zg9aAF1rD7e1qGgFwCGCAPYtS-zCp_zA0iw@mail.gmail.com>
2022-06-08  7:34     ` Willy Tarreau
2022-06-13  2:09       ` Feng Tang
2022-06-13 17:10         ` Eric Dumazet
2022-06-14  0:42           ` Feng Tang

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=20220608064822.GC7547@1wt.eu \
    --to=w@1wt.eu \
    --cc=aksecurity@gmail.com \
    --cc=edumazet@google.com \
    --cc=feng.tang@intel.com \
    --cc=fengwei.yin@intel.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=moshe.kol@mail.huji.ac.il \
    --cc=netdev@vger.kernel.org \
    --cc=oliver.sang@intel.com \
    --cc=ying.huang@intel.com \
    --cc=yossi.gilad@mail.huji.ac.il \
    --cc=zhengjun.xing@linux.intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).