[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5d4fbe21-7959-d53f-76c5-ed0299d8db23@intel.com>
Date: Thu, 14 May 2020 13:12:18 +0800
From: Rong Chen <rong.a.chen@...el.com>
To: Christian Kujau <lists@...dbynature.de>
Cc: Jia-Ju Bai <baijiaju1990@...il.com>, shaggy@...nel.org,
jfs-discussion@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
lkp@...ts.01.org, Markus.Elfring@....de
Subject: Re: [Jfs-discussion] [fs] 05c5a0273b: netperf.Throughput_total_tps
-71.8% regression
On 5/14/20 12:27 PM, Christian Kujau wrote:
> On Tue, 12 May 2020, kernel test robot wrote:
>> FYI, we noticed a -71.8% regression of netperf.Throughput_total_tps due to commit:
> As noted in this report, netperf is used to "measure various aspect of
> networking performance". Are we sure the bisect is correct? JFS is a
> filesystem and is not touching net/ in any way. So, having not attempted
> to reproduce this, maybe the JFS commit is a red herring?
>
> C.
Hi,
The commit also causes -74.6% regression of will-it-scale.per_thread_ops:
in testcase: will-it-scale
on test machine: 8 threads Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz with 16G memory
with following parameters:
nr_task: 100%
mode: thread
test: unlink2
cpufreq_governor: performance
ucode: 0x21
I'll send another report for this regression.
Best Regards,
Rong Chen
Powered by blists - more mailing lists