From: Paolo Abeni <pabeni@redhat.com>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [udp] bc0d3d0639: apachebench.requests_per_second -21% regression
Date: Fri, 09 Jun 2017 17:35:29 +0200 [thread overview]
Message-ID: <1497022529.3416.16.camel@redhat.com> (raw)
In-Reply-To: <1496871606.2593.2.camel@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 776 bytes --]
On Wed, 2017-06-07 at 23:40 +0200, Paolo Abeni wrote:
> 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?
I did a lot of run of the ab test tool, on both vanilla and patched
kernel and I measured a variance well above 21% and a very similar
distribution for both vanilla and patched kernel. I'm really thinking
this is a test-suite artifact.
How do you a get stable baseline?
Thank you,
Paolo
next prev parent reply other threads:[~2017-06-09 15:35 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
2017-06-09 15:35 ` Paolo Abeni [this message]
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=1497022529.3416.16.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.