From: Waiman Long <longman@redhat.com>
To: kernel test robot <oliver.sang@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org, Davidlohr Bueso <dave@stgolabs.net>,
Phil Auld <pauld@redhat.com>, 0day robot <lkp@intel.com>,
lkp@lists.01.org, ying.huang@intel.com, feng.tang@intel.com,
zhengjun.xing@intel.com
Subject: Re: [locking/rwsem] 10a59003d2: unixbench.score -25.5% regression
Date: Mon, 23 Nov 2020 14:28:23 -0500 [thread overview]
Message-ID: <2fe05c84-fe0b-c7da-7ba8-c5bac2e6fb56@redhat.com> (raw)
In-Reply-To: <20201123155327.GA26172@xsang-OptiPlex-9020>
On 11/23/20 10:53 AM, kernel test robot wrote:
>
> Greeting,
>
> FYI, we noticed a -25.5% regression of unixbench.score due to commit:
>
>
> commit: 10a59003d29fbfa855b2ef4f3534fee9bdf4e575 ("[PATCH v2 5/5] locking/rwsem: Remove reader optimistic spinning")
> url: https://github.com/0day-ci/linux/commits/Waiman-Long/locking-rwsem-Rework-reader-optimistic-spinning/20201121-122118
> base: https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git 932f8c64d38bb08f69c8c26a2216ba0c36c6daa8
>
> in testcase: unixbench
> on test machine: 16 threads Intel(R) Xeon(R) E-2278G CPU @ 3.40GHz with 32G memory
> with following parameters:
>
> runtime: 300s
> nr_task: 30%
> test: shell8
> cpufreq_governor: performance
> ucode: 0xde
>
> test-description: UnixBench is the original BYTE UNIX benchmark suite aims to test performance of Unix-like system.
> test-url: https://github.com/kdlucas/byte-unixbench
>
> In addition to that, the commit also has significant impact on the following tests:
>
> +------------------+---------------------------------------------------------------------------+
> | testcase: change | fio-basic: fio.write_iops -29.9% regression |
> | test machine | 192 threads Intel(R) Xeon(R) CPU @ 2.20GHz with 192G memory |
> | test parameters | bs=4k |
> | | cpufreq_governor=performance |
> | | disk=1SSD |
> | | fs=xfs |
> | | ioengine=sync |
> | | nr_task=32 |
> | | runtime=300s |
> | | rw=randwrite |
> | | test_size=256g |
> | | ucode=0x4003003 |
> +------------------+---------------------------------------------------------------------------+
> | testcase: change | aim7: aim7.jobs-per-min 952.6% improvement |
> | test machine | 96 threads Intel(R) Xeon(R) Platinum 8260L CPU @ 2.40GHz with 128G memory |
> | test parameters | cpufreq_governor=performance |
> | | disk=4BRD_12G |
> | | fs=f2fs |
> | | load=100 |
> | | md=RAID0 |
> | | test=sync_disk_rw |
> | | ucode=0x4003003 |
> +------------------+---------------------------------------------------------------------------+
A performance drop in some benchmark is expected. However, there are
others that can show improvement. Will take a look to see if we can
reduce the performance regression.
Thanks,
Longman
next prev parent reply other threads:[~2020-11-23 19:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 4:14 [PATCH v2 0/5] locking/rwsem: Rework reader optimistic spinning Waiman Long
2020-11-21 4:14 ` [PATCH v2 1/5] locking/rwsem: Pass the current atomic count to rwsem_down_read_slowpath() Waiman Long
2020-12-09 18:38 ` [tip: locking/core] " tip-bot2 for Waiman Long
2020-11-21 4:14 ` [PATCH v2 2/5] locking/rwsem: Prevent potential lock starvation Waiman Long
2020-11-26 8:12 ` [locking/rwsem] 25d0c60b0e: vm-scalability.throughput 316.2% improvement kernel test robot
2020-12-09 18:38 ` [tip: locking/core] locking/rwsem: Prevent potential lock starvation tip-bot2 for Waiman Long
2020-11-21 4:14 ` [PATCH v2 3/5] locking/rwsem: Enable reader optimistic lock stealing Waiman Long
2020-12-09 18:38 ` [tip: locking/core] " tip-bot2 for Waiman Long
2020-11-21 4:14 ` [PATCH v2 4/5] locking/rwsem: Wake up all waiting readers if RWSEM_WAKE_READ_OWNED Waiman Long
2020-11-24 3:15 ` [locking/rwsem] c9847a7f94: aim7.jobs-per-min -91.8% regression kernel test robot
2020-11-21 4:14 ` [PATCH v2 5/5] locking/rwsem: Remove reader optimistic spinning Waiman Long
2020-11-23 15:53 ` [locking/rwsem] 10a59003d2: unixbench.score -25.5% regression kernel test robot
2020-11-23 19:28 ` Waiman Long [this message]
2020-12-08 3:56 ` [PATCH v2 5/5] locking/rwsem: Remove reader optimistic spinning Davidlohr Bueso
2020-12-08 10:07 ` Peter Zijlstra
2020-12-08 15:29 ` Waiman Long
2020-12-09 18:38 ` [tip: locking/core] " tip-bot2 for Waiman Long
2020-12-08 14:57 ` [PATCH v2 0/5] locking/rwsem: Rework " Peter Zijlstra
2020-12-08 16:33 ` Waiman Long
2020-12-08 17:02 ` Peter Zijlstra
2020-12-08 17:30 ` Waiman Long
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=2fe05c84-fe0b-c7da-7ba8-c5bac2e6fb56@redhat.com \
--to=longman@redhat.com \
--cc=dave@stgolabs.net \
--cc=feng.tang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=mingo@redhat.com \
--cc=oliver.sang@intel.com \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
--cc=ying.huang@intel.com \
--cc=zhengjun.xing@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
all inboxes | Powered by JetHome®