From: Brandon Lo <blo@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
dpdklab@iol.unh.edu, 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] [dpdklab] Re: Intel performance test is failing
Date: Tue, 3 Mar 2020 09:13:44 -0500
Message-ID: <CAOeXdvazxYtF04Q7yGhge=E83cT=LBMRVQa1Vxz=pvf-A6UG6A@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8xKzS6pGT9JdQtyUyF3cAJGNN=n1Gvbdqp8DrAaYbiYQw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1691 bytes --]
Hi David and Zhaoyan,
>
Yes, those results are related to the Intel machine; I have disabled
testing for the Intel testbed.
The 82599ES machine is now available for ssh and modifications.
Thanks
On Tue, Mar 3, 2020 at 4:22 AM David Marchand <david.marchand@redhat.com>
wrote:
> 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
>
--
Brandon Lo
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
blo@iol.unh.edu
www.iol.unh.edu
[-- Attachment #2: Type: text/html, Size: 5789 bytes --]
<div dir="ltr">Hi David and Zhaoyan,<div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"></blockquote><div><br></div><div>Yes, those results are related to the Intel machine; I have disabled testing for the Intel testbed.</div><div><br></div><div>The 82599ES machine is now available for ssh and modifications.</div><div><br></div><div>Thanks</div><div><br></div><div><br></div><div><br></div><div> </div><div><br></div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar 3, 2020 at 4:22 AM David Marchand <<a href="mailto:david.marchand@redhat.com">david.marchand@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Feb 3, 2020 at 4:58 AM Chen, Zhaoyan <<a href="mailto:zhaoyan.chen@intel.com" target="_blank">zhaoyan.chen@intel.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif;color:rgb(31,73,125)">Thanks Jeremy.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif;color:rgb(31,73,125)">I quickly checked per-patches results and logs for the failures. That seems not always failed case.. like fluctuation.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif;color:rgb(31,73,125)">For this case, could you help to check<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif;color:rgb(31,73,125)">- if BIOS’s turbo boost is off, C0/C1 is off, C6 is off<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif;color:rgb(31,73,125)">- if cores’ are isolated in kernel’s parameter<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif;color:rgb(31,73,125)">- if other tasks are scheduled on the testbed when running performance test<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif;color:rgb(31,73,125)">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). <u></u><u></u></span></p>
</div></div></blockquote><div><br></div><div>(replaced jeremy @mail with the dpdklab alias).<br></div><div><br></div><div>Is this issue linked to the failures I see?</div><div><br></div><div><a href="https://lab.dpdk.org/results/dashboard/patchsets/9799/" target="_blank">https://lab.dpdk.org/results/dashboard/patchsets/9799/</a><br><a href="https://lab.dpdk.org/results/dashboard/patchsets/9800/" target="_blank">https://lab.dpdk.org/results/dashboard/patchsets/9800/</a><br><a href="https://lab.dpdk.org/results/dashboard/patchsets/9804/" target="_blank">https://lab.dpdk.org/results/dashboard/patchsets/9804/</a><br><a href="https://lab.dpdk.org/results/dashboard/patchsets/9809/" target="_blank">https://lab.dpdk.org/results/dashboard/patchsets/9809/</a><br><a href="https://lab.dpdk.org/results/dashboard/patchsets/9814/" target="_blank">https://lab.dpdk.org/results/dashboard/patchsets/9814/</a><br><a href="https://lab.dpdk.org/results/dashboard/patchsets/9820/" target="_blank">https://lab.dpdk.org/results/dashboard/patchsets/9820/</a></div><div><br></div><div><br></div><div>Thanks.</div><div><br> </div><div>-- <br></div><div>David Marchand<br></div></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><span><p dir="ltr" style="line-height:1.2;margin-top:0pt;margin-bottom:0pt"><span style="font-size:10pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">Brandon Lo</span></p><p dir="ltr" style="line-height:1.2;margin-top:0pt;margin-bottom:0pt"><span style="font-size:10pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">UNH InterOperability Laboratory</span></p><p dir="ltr" style="line-height:1.2;margin-top:0pt;margin-bottom:0pt"><span style="font-size:10pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">21 Madbury Rd, Suite 100, Durham, NH 03824</span></p><p dir="ltr" style="line-height:1.2;margin-top:0pt;margin-bottom:0pt"><span style="font-size:10pt;font-family:Arial;color:rgb(17,85,204);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><a href="mailto:blo@iol.unh.edu" target="_blank">blo@iol.unh.edu</a></span></p><p dir="ltr" style="line-height:1.2;margin-top:0pt;margin-bottom:0pt"><span style="font-size:10pt;font-family:Arial;color:rgb(17,85,204);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><a href="http://www.iol.unh.edu/" target="_blank">www.iol.unh.edu</a></span></p></span></div></div></div></div>
next prev parent reply index
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 15:58 [dpdk-ci] " 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
2020-03-03 14:13 ` Brandon Lo [this message]
2020-03-10 9:32 ` [dpdk-ci] [dpdklab] " 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 publically 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='CAOeXdvazxYtF04Q7yGhge=E83cT=LBMRVQa1Vxz=pvf-A6UG6A@mail.gmail.com' \
--to=blo@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--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
DPDK CI discussions
Archives are clonable:
git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
ci@dpdk.org
public-inbox-index ci
Newsgroup available over NNTP:
nntp://inbox.dpdk.org/inbox.dpdk.ci
AGPL code for this site: git clone https://public-inbox.org/ public-inbox