From: David Marchand <david.marchand@redhat.com>
To: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>, dpdklab@iol.unh.edu
Cc: Lincoln Lavoie <lylavoie@iol.unh.edu>,
Thomas Monjalon <thomas@monjalon.net>,
"ci@dpdk.org" <ci@dpdk.org>, "Tu, Lijuan" <lijuan.tu@intel.com>,
"Xu, Qian Q" <qian.q.xu@intel.com>
Subject: Re: [dpdk-ci] Intel performance test is failing
Date: Tue, 3 Mar 2020 10:21:42 +0100 [thread overview]
Message-ID: <CAJFAV8xKzS6pGT9JdQtyUyF3cAJGNN=n1Gvbdqp8DrAaYbiYQw@mail.gmail.com> (raw)
In-Reply-To: <9DEEADBC57E43F4DA73B571777FECECA41EBB4AF@SHSMSX104.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
On Mon, Feb 3, 2020 at 4:58 AM Chen, Zhaoyan <zhaoyan.chen@intel.com> wrote:
> Thanks Jeremy.
>
>
>
> I quickly checked per-patches results and logs for the failures. That
> seems not always failed case.. like fluctuation.
>
>
>
> For this case, could you help to check
>
> - if BIOS’s turbo boost is off, C0/C1 is off, C6 is off
>
> - if cores’ are isolated in kernel’s parameter
>
> - if other tasks are scheduled on the testbed when running performance test
>
>
>
> If all settings are good, we may consider it’s a regression or unstable
> performance issue. We will double check the performance by IXIA with latest
> DPDK master when we back to office (1 week later).
>
(replaced jeremy @mail with the dpdklab alias).
Is this issue linked to the failures I see?
https://lab.dpdk.org/results/dashboard/patchsets/9799/
https://lab.dpdk.org/results/dashboard/patchsets/9800/
https://lab.dpdk.org/results/dashboard/patchsets/9804/
https://lab.dpdk.org/results/dashboard/patchsets/9809/
https://lab.dpdk.org/results/dashboard/patchsets/9814/
https://lab.dpdk.org/results/dashboard/patchsets/9820/
Thanks.
--
David Marchand
[-- Attachment #2: Type: text/html, Size: 3382 bytes --]
next prev parent reply other threads:[~2020-03-03 9:22 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 15:58 Thomas Monjalon
2020-01-23 16:25 ` Jeremy Plsek
2020-01-23 20:28 ` Lincoln Lavoie
2020-01-31 3:17 ` Chen, Zhaoyan
2020-01-31 14:48 ` Jeremy Plsek
2020-02-03 3:57 ` Chen, Zhaoyan
2020-03-03 9:21 ` David Marchand [this message]
2020-03-03 14:13 ` [dpdk-ci] [dpdklab] " Brandon Lo
2020-03-10 9:32 ` David Marchand
2020-03-10 13:11 ` Brandon Lo
2020-03-10 14:46 ` Brandon Lo
2020-03-11 2:13 ` Chen, Zhaoyan
2020-03-17 19:34 ` Brandon Lo
2020-03-18 13:04 ` Chen, Zhaoyan
2020-03-20 1:35 ` Chen, Zhaoyan
2020-03-20 17:48 ` Brandon Lo
2020-03-23 1:58 ` Chen, Zhaoyan
2020-03-24 13:30 ` Brandon Lo
2020-03-25 4:59 ` Chen, Zhaoyan
2020-03-26 15:39 ` Brandon Lo
2020-03-30 4:43 ` Chen, Zhaoyan
2020-03-31 13:42 ` Brandon Lo
2020-04-01 6:00 ` Ma, LihongX
2020-04-02 18:39 ` Brandon Lo
2020-04-03 1:14 ` Ma, LihongX
2020-04-15 9:39 ` Ma, LihongX
2020-04-15 19:30 ` Brandon Lo
2020-04-16 3:40 ` Ma, LihongX
2020-04-16 15:04 ` Brandon Lo
2020-04-17 1:54 ` Ma, LihongX
2020-04-17 7:00 ` Ma, LihongX
2020-04-17 15:52 ` Brandon Lo
2020-04-18 1:13 ` Ma, LihongX
2020-04-28 3:39 ` Ma, LihongX
2020-04-28 16:51 ` Brandon Lo
2020-04-29 5:30 ` Ma, LihongX
2020-04-30 14:19 ` Brandon Lo
2020-05-06 13:05 ` Brandon Lo
2020-05-08 8:02 ` Ma, LihongX
2020-05-12 5:41 ` Ma, LihongX
2020-05-14 16:12 ` Brandon Lo
2020-05-15 1:30 ` Ma, LihongX
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='CAJFAV8xKzS6pGT9JdQtyUyF3cAJGNN=n1Gvbdqp8DrAaYbiYQw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=ci@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--cc=lijuan.tu@intel.com \
--cc=lylavoie@iol.unh.edu \
--cc=qian.q.xu@intel.com \
--cc=thomas@monjalon.net \
--cc=zhaoyan.chen@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;
as well as URLs for NNTP newsgroup(s).