From: kernel test robot <xiaolong.ye@intel.com>
To: Xishi Qiu <qiuxishi@huawei.com>
Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Joonsoo Kim <js1304@gmail.com>,
David Rientjes <rientjes@google.com>,
Laura Abbott <lauraa@codeaurora.org>, Hui Zhu <zhuhui@xiaomi.com>,
Wang Xiaoqiang <wangxq10@lzu.edu.cn>,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: [lkp] [mm] 6f25a14a70: will-it-scale.scalability -4.0% regression
Date: Thu, 7 Apr 2016 09:06:57 +0800 [thread overview]
Message-ID: <20160407010657.GB12139@yexl-desktop> (raw)
[-- Attachment #1: Type: text/plain, Size: 1709 bytes --]
FYI, we noticed that will-it-scale.scalability -4.0% regression on
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit 6f25a14a7053b69917e2ebea0d31dd444cd31fd5 ("mm: fix invalid node in alloc_migrate_target()")
=========================================================================================
compiler/cpufreq_governor/kconfig/rootfs/tbox_group/test/testcase:
gcc-4.9/performance/x86_64-rhel/debian-x86_64-2015-02-07.cgz/lkp-ivb-d03/pthread_mutex1/will-it-scale
commit:
969e8d7e47f93ef693028667480558de8f70523f
6f25a14a7053b69917e2ebea0d31dd444cd31fd5
969e8d7e47f93ef6 6f25a14a7053b69917e2ebea0d
---------------- --------------------------
fail:runs %reproduction fail:runs
%stddev %change %stddev
\ | \
2.032e+08 ± 0% -1.6% 2e+08 ± 0% will-it-scale.per_process_ops
0.83 ± 0% -4.0% 0.79 ± 0% will-it-scale.scalability
214103 ± 14% -20.2% 170884 ± 14% sched_debug.cpu.ttwu_count.stddev
3789 ± 7% -10.3% 3398 ± 6% slabinfo.anon_vma_chain.active_objs
4660 ± 5% +7.7% 5019 ± 2% vmstat.system.in
lkp-ivb-d03: Ivy Bridge
Memory: 4G
To reproduce:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
cd lkp-tests
bin/lkp install job.yaml # job file is attached in this email
bin/lkp run job.yaml
Disclaimer:
Results have been estimated based on internal Intel analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Xiaolong Ye
[-- Attachment #2: job.yaml --]
[-- Type: text/plain, Size: 3497 bytes --]
---
LKP_SERVER: inn
LKP_CGI_PORT: 80
LKP_CIFS_PORT: 139
testcase: will-it-scale
default-monitors:
wait: activate-monitor
kmsg:
uptime:
iostat:
heartbeat:
vmstat:
numa-numastat:
numa-vmstat:
numa-meminfo:
proc-vmstat:
proc-stat:
interval: 10
meminfo:
slabinfo:
interrupts:
lock_stat:
latency_stats:
softirqs:
bdi_dev_mapping:
diskstats:
nfsstat:
cpuidle:
cpufreq-stats:
turbostat:
pmeter:
sched_debug:
interval: 60
cpufreq_governor: performance
default-watchdogs:
oom-killer:
watchdog:
commit: 6f25a14a7053b69917e2ebea0d31dd444cd31fd5
model: Ivy Bridge
nr_cpu: 4
memory: 4G
nr_hdd_partitions: 0
hdd_partitions:
netconsole_port: 6674
category: benchmark
perf-profile:
freq: 800
will-it-scale:
test: pthread_mutex1
queue: bisect
testbox: lkp-ivb-d03
tbox_group: lkp-ivb-d03
kconfig: x86_64-rhel
enqueue_time: 2016-04-05 08:13:46.122054989 +08:00
compiler: gcc-4.9
rootfs: debian-x86_64-2015-02-07.cgz
id: 4d65b9ec0610d8e0e7fe68094c43e3fb8d15f831
user: lkp
head_commit: c41dbbf6f591a0269b815b2eb5f2a15aae948e52
base_commit: 9735a22799b9214d17d3c231fe377fc852f042e9
branch: internal-eywa/master
result_root: "/result/will-it-scale/performance-pthread_mutex1/lkp-ivb-d03/debian-x86_64-2015-02-07.cgz/x86_64-rhel/gcc-4.9/6f25a14a7053b69917e2ebea0d31dd444cd31fd5/0"
job_file: "/lkp/scheduled/lkp-ivb-d03/bisect_will-it-scale-performance-pthread_mutex1-debian-x86_64-2015-02-07.cgz-x86_64-rhel-6f25a14a7053b69917e2ebea0d31dd444cd31fd5-20160405-76887-1te91eg-0.yaml"
max_uptime: 1500
initrd: "/osimage/debian/debian-x86_64-2015-02-07.cgz"
bootloader_append:
- root=/dev/ram0
- user=lkp
- job=/lkp/scheduled/lkp-ivb-d03/bisect_will-it-scale-performance-pthread_mutex1-debian-x86_64-2015-02-07.cgz-x86_64-rhel-6f25a14a7053b69917e2ebea0d31dd444cd31fd5-20160405-76887-1te91eg-0.yaml
- ARCH=x86_64
- kconfig=x86_64-rhel
- branch=internal-eywa/master
- commit=6f25a14a7053b69917e2ebea0d31dd444cd31fd5
- BOOT_IMAGE=/pkg/linux/x86_64-rhel/gcc-4.9/6f25a14a7053b69917e2ebea0d31dd444cd31fd5/vmlinuz-4.6.0-rc1-00068-g6f25a14
- max_uptime=1500
- RESULT_ROOT=/result/will-it-scale/performance-pthread_mutex1/lkp-ivb-d03/debian-x86_64-2015-02-07.cgz/x86_64-rhel/gcc-4.9/6f25a14a7053b69917e2ebea0d31dd444cd31fd5/0
- LKP_SERVER=inn
- |2-
earlyprintk=ttyS0,115200 systemd.log_level=err
debug apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100
panic=-1 softlockup_panic=1 nmi_watchdog=panic oops=panic load_ramdisk=2 prompt_ramdisk=0
console=ttyS0,115200 console=tty0 vga=normal
rw
lkp_initrd: "/lkp/lkp/lkp-x86_64.cgz"
modules_initrd: "/pkg/linux/x86_64-rhel/gcc-4.9/6f25a14a7053b69917e2ebea0d31dd444cd31fd5/modules.cgz"
bm_initrd: "/osimage/deps/debian-x86_64-2015-02-07.cgz/lkp.cgz,/osimage/deps/debian-x86_64-2015-02-07.cgz/run-ipconfig.cgz,/osimage/deps/debian-x86_64-2015-02-07.cgz/turbostat.cgz,/lkp/benchmarks/turbostat.cgz,/osimage/deps/debian-x86_64-2015-02-07.cgz/will-it-scale.cgz,/lkp/benchmarks/will-it-scale.cgz,/lkp/benchmarks/will-it-scale-x86_64.cgz"
linux_headers_initrd: "/pkg/linux/x86_64-rhel/gcc-4.9/6f25a14a7053b69917e2ebea0d31dd444cd31fd5/linux-headers.cgz"
repeat_to: 2
kernel: "/pkg/linux/x86_64-rhel/gcc-4.9/6f25a14a7053b69917e2ebea0d31dd444cd31fd5/vmlinuz-4.6.0-rc1-00068-g6f25a14"
dequeue_time: 2016-04-05 08:15:41.011882855 +08:00
job_state: finished
loadavg: 3.03 1.65 0.68 1/115 4702
start_time: '1459815369'
end_time: '1459815673'
version: "/lkp/lkp/.src-20160401-231508"
[-- Attachment #3: reproduce --]
[-- Type: text/plain, Size: 436 bytes --]
2016-04-05 08:16:08 echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
2016-04-05 08:16:08 echo performance > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
2016-04-05 08:16:08 echo performance > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
2016-04-05 08:16:08 echo performance > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
2016-04-05 08:16:09 ./runtest.py pthread_mutex1 32 both 1 2 3 4
next reply other threads:[~2016-04-07 1:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 1:06 kernel test robot [this message]
2016-04-07 2:40 ` Xishi Qiu
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=20160407010657.GB12139@yexl-desktop \
--to=xiaolong.ye@intel.com \
--cc=js1304@gmail.com \
--cc=lauraa@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=qiuxishi@huawei.com \
--cc=rientjes@google.com \
--cc=wangxq10@lzu.edu.cn \
--cc=zhuhui@xiaomi.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®