From: Paolo Abeni <pabeni@redhat.com>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [udp] bc0d3d0639: apachebench.requests_per_second -21% regression
Date: Wed, 07 Jun 2017 23:40:06 +0200 [thread overview]
Message-ID: <1496871606.2593.2.camel@redhat.com> (raw)
In-Reply-To: <20170607021229.GJ2969@yexl-desktop>
[-- Attachment #1: Type: text/plain, Size: 2138 bytes --]
Hi,
On Wed, 2017-06-07 at 10:12 +0800, kernel test robot wrote:
> To reproduce:
>
> git clone https://github.com/01org/lkp-tests.git
> cd lkp-tests
> bin/lkp install job.yaml # job file is attached in this email
> bin/lkp run job.yaml
I tried to reproduce the tests with the above steps, and I have a few
questions.
On a centos 7.3 distro I get (after a successful install step)
# bin/lkp run ~/job.yaml
2017-06-07 12:18:39
for cpu_dir in /sys/devices/system/cpu/cpu[0-9]*
do
online_file="$cpu_dir"/online
[ -f "$online_file" ] && [ "$(cat "$online_file")" -eq 0 ] && continue
file="$cpu_dir"/cpufreq/scaling_governor
[ -f "$file" ] && echo "$scaling_governor" > "$file"
done
IPMI Device Information
kill 5398 vmstat --timestamp -n 10
kill 5393 dmesg --follow --decode
kill 5540 mpstat 1
kill 5534 /usr/bin/perf stat -a -I 1000 -x -e cpu-clock,task-clock,page-faults,context-switches,cpu-migrations,minor-faults,major-faults --log-fd 1 --
kill 5402 vmstat --timestamp -n 1
wait for background monitors: 5504 5527 5458 5477 5434 5445 5426 5489 5451 5558 5573 5521 5550 cpuidle sched_debug interrupts softirqs proc-stat meminfo proc-vmstat diskstats slabinfo oom-killer nfs-hang turbostat perf-profile
Error:
The /tmp/lkp-root/perf.data file has no samples!
Do I need any additional setup?
I tried to measure the regression using the Apache benchmarking tool
directly with:
ab -t 300 -c 1000 -n 1000000 -q -k http://127.0.0.1/
and, across the named patches I see no relevant differences, and
(oddly enough) some measurable improvement vs the vanilla linux-net.
Can the measured regression be caused by some fuzz in the test
environment, like the test being run on different HW?
Finally I recently posted a v2 of the relevant series, will that go
through the same tests? Can I please get notified in case the series
pass the test without regressions? (I assume an email similar to the
previous one will be sent in case of failure).
Thank you,
Paolo
next prev parent reply other threads:[~2017-06-07 21:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 15:27 [PATCH net-next 0/3] udp: reduce cache pressure Paolo Abeni
2017-05-29 15:27 ` [PATCH net-next 1/3] net: factor out a helper to decrement the skb refcount Paolo Abeni
2017-05-31 16:56 ` Eric Dumazet
2017-05-29 15:27 ` [PATCH net-next 2/3] udp: avoid a cache miss on dequeue Paolo Abeni
2017-05-31 17:00 ` Eric Dumazet
2017-06-01 10:39 ` Paolo Abeni
2017-06-01 15:58 ` Eric Dumazet
2017-06-01 16:21 ` Paolo Abeni
2017-06-01 16:40 ` Eric Dumazet
2017-06-01 20:35 ` Paolo Abeni
2017-06-01 20:50 ` Eric Dumazet
2017-05-29 15:27 ` [PATCH net-next 3/3] udp: try to avoid 2 " Paolo Abeni
2017-05-31 17:04 ` Eric Dumazet
2017-06-01 10:46 ` Paolo Abeni
2017-06-07 2:12 ` [lkp-robot] [udp] bc0d3d0639: apachebench.requests_per_second -21% regression kernel test robot
2017-06-07 2:12 ` kernel test robot
2017-06-07 21:40 ` Paolo Abeni [this message]
2017-06-09 15:35 ` Paolo Abeni
2017-06-30 6:55 ` Ye Xiaolong
2017-05-31 16:47 ` [PATCH net-next 0/3] udp: reduce cache pressure David Miller
2017-05-31 16:52 ` Eric Dumazet
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=1496871606.2593.2.camel@redhat.com \
--to=pabeni@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.