DPDK CI discussions
 help / color / Atom feed
From: Jeremy Plsek <jplsek@iol.unh.edu>
To: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>
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: Fri, 31 Jan 2020 09:48:12 -0500
Message-ID: <CA+xUZB7CORnkzAZR_x9uN43AfJHwzvgpF66F0WdiQ+t3PdC7AA@mail.gmail.com> (raw)
In-Reply-To: <9DEEADBC57E43F4DA73B571777FECECA41EAB066@SHSMSX104.ccr.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 3285 bytes --]

It's possible this is happening more frequently because of enabling
overlayfs.
We also changed how the baseline is retrieved because of the overlayfs
system, but this issue was happening before this change.
I think this started happening after a few months after upgrading to Ubuntu
18.04.

Here are the recent results (login to view and download the artifacts):
https://lab.dpdk.org/results/dashboard/patchsets/9344/#env-19
https://lab.dpdk.org/results/dashboard/patchsets/9343/#env-19
https://lab.dpdk.org/results/dashboard/patchsets/9340/#env-19

Here are some results that were "off" (see the "Run 1" tab):
https://lab.dpdk.org/results/dashboard/patchsets/9346/#env-19
https://lab.dpdk.org/results/dashboard/patchsets/9331/#env-19
https://lab.dpdk.org/results/dashboard/patchsets/9321/#env-19

And here are some older tests where this occurred:
https://lab.dpdk.org/results/dashboard/patchsets/8813/#env-19
https://lab.dpdk.org/results/dashboard/patchsets/8795/#env-19

I also found some tests where it happened on the 40g platform:
https://lab.dpdk.org/results/dashboard/patchsets/9188/#env-18
https://lab.dpdk.org/results/dashboard/patchsets/8870/#env-18
(older, before enabling overlayfs):
https://lab.dpdk.org/results/dashboard/patchsets/7665/#env-18
https://lab.dpdk.org/results/dashboard/patchsets/7653/#env-18


On Thu, Jan 30, 2020 at 10:17 PM Chen, Zhaoyan <zhaoyan.chen@intel.com>
wrote:

> Hi, Jeremy and Lincoln,
>
>
>
> Did you change anything on the Intel testbed? DTS code or testbed
> environment?
>
> And could you send me the detailed test logs? We will do a quick check.
>
>
>
> Thanks
>
>
>
>
>
> *Regards,*
>
> *Zhaoyan Chen*
>
>
>
> *From:* Lincoln Lavoie <lylavoie@iol.unh.edu>
> *Sent:* Friday, January 24, 2020 4:29 AM
> *To:* Jeremy Plsek <jplsek@iol.unh.edu>
> *Cc:* Thomas Monjalon <thomas@monjalon.net>; ci@dpdk.org; Tu, Lijuan <
> lijuan.tu@intel.com>; Chen, Zhaoyan <zhaoyan.chen@intel.com>; Xu, Qian Q <
> qian.q.xu@intel.com>
> *Subject:* Re: [dpdk-ci] Intel performance test is failing
>
>
>
> In the "off cases," is that specific to that hardware, or does it happen
> on all hardware variants from time-to-time?
>
>
>
> On Thu, Jan 23, 2020 at 11:25 AM Jeremy Plsek <jplsek@iol.unh.edu> wrote:
>
> On Thu, Jan 23, 2020 at 11:06 AM Thomas Monjalon <thomas@monjalon.net>
> wrote:
> >
> > Hi,
> >
> > The test iol-intel-Performance is failing on all patches
> > for a couple of days.
> > It seems to be due to a perf drop with a 10G device
> >
> > Can we disable this test until we understand what happens?
> >
> > We need also to understand how to avoid such failure,
> > and how to monitor and disable it faster.
> >
> > Thanks
> >
> >
> Hi Thomas,
>
> I've disabled it for now until someone from the Intel team can look
> into it (cc'd).
>
> I've also seem problems where the results are completely off
> (-15mpps), and I've been rerunning those when they happen. I'm hoping
> those can be resolved too.
>
> --
> Jeremy Plsek
> UNH InterOperability Laboratory
>
>
>
>
> --
>
> *Lincoln Lavoie*
>
> Senior Engineer, Broadband Technologies
>
> 21 Madbury Rd., Ste. 100, Durham, NH 03824
>
> lylavoie@iol.unh.edu
>
> https://www.iol.unh.edu
>
> +1-603-674-2755 (m)
>
> <https://www.iol.unh.edu/>
>


-- 
Jeremy Plsek
UNH InterOperability Laboratory

[-- Attachment #2: Type: text/html, Size: 9225 bytes --]

<div dir="ltr"><div>It&#39;s possible this is happening more frequently because of enabling overlayfs.</div><div>We also changed how the baseline is retrieved because of the overlayfs system, but this issue was happening before this change.</div><div>I think this started happening after a few months after upgrading to Ubuntu 18.04.<br></div><div><br></div><div>Here are the recent results (login to view and download the artifacts):</div><div><a href="https://lab.dpdk.org/results/dashboard/patchsets/9344/#env-19">https://lab.dpdk.org/results/dashboard/patchsets/9344/#env-19</a></div><div><a href="https://lab.dpdk.org/results/dashboard/patchsets/9343/#env-19">https://lab.dpdk.org/results/dashboard/patchsets/9343/#env-19</a></div><div><a href="https://lab.dpdk.org/results/dashboard/patchsets/9340/#env-19">https://lab.dpdk.org/results/dashboard/patchsets/9340/#env-19</a></div><div><br></div><div>Here are some results that were &quot;off&quot; (see the &quot;Run 1&quot; tab):</div><div><a href="https://lab.dpdk.org/results/dashboard/patchsets/9346/#env-19">https://lab.dpdk.org/results/dashboard/patchsets/9346/#env-19</a></div><div><a href="https://lab.dpdk.org/results/dashboard/patchsets/9331/#env-19">https://lab.dpdk.org/results/dashboard/patchsets/9331/#env-19</a></div><div><a href="https://lab.dpdk.org/results/dashboard/patchsets/9321/#env-19">https://lab.dpdk.org/results/dashboard/patchsets/9321/#env-19</a></div><div><br></div><div>And here are some older tests where this occurred:</div><div><a href="https://lab.dpdk.org/results/dashboard/patchsets/8813/#env-19">https://lab.dpdk.org/results/dashboard/patchsets/8813/#env-19</a><div><a href="https://lab.dpdk.org/results/dashboard/patchsets/8795/#env-19">https://lab.dpdk.org/results/dashboard/patchsets/8795/#env-19</a></div><div><br></div><div>I also found some tests where it happened on the 40g platform:</div><div><a href="https://lab.dpdk.org/results/dashboard/patchsets/9188/#env-18">https://lab.dpdk.org/results/dashboard/patchsets/9188/#env-18</a></div><div><a href="https://lab.dpdk.org/results/dashboard/patchsets/8870/#env-18">https://lab.dpdk.org/results/dashboard/patchsets/8870/#env-18</a></div><div>(older, before enabling overlayfs):</div><div><a href="https://lab.dpdk.org/results/dashboard/patchsets/7665/#env-18">https://lab.dpdk.org/results/dashboard/patchsets/7665/#env-18</a></div><div><a href="https://lab.dpdk.org/results/dashboard/patchsets/7653/#env-18">https://lab.dpdk.org/results/dashboard/patchsets/7653/#env-18</a></div></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 30, 2020 at 10:17 PM Chen, Zhaoyan &lt;<a href="mailto:zhaoyan.chen@intel.com">zhaoyan.chen@intel.com</a>&gt; 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 class="gmail-m_-5920278011901207711WordSection1">
<p class="MsoNormal"><span style="font-family:&quot;Calibri Light&quot;,sans-serif;color:rgb(31,73,125)">Hi, Jeremy and Lincoln,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:&quot;Calibri Light&quot;,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:&quot;Calibri Light&quot;,sans-serif;color:rgb(31,73,125)">Did you change anything on the Intel testbed? DTS code or testbed environment?
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:&quot;Calibri Light&quot;,sans-serif;color:rgb(31,73,125)">And could you send me the detailed test logs? We will do a quick check.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:&quot;Calibri Light&quot;,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:&quot;Calibri Light&quot;,sans-serif;color:rgb(31,73,125)">Thanks<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:&quot;Calibri Light&quot;,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><i><span style="font-size:10pt;font-family:&quot;Calibri Light&quot;,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></i></p>
<p class="MsoNormal"><i><span style="font-family:&quot;Calibri Light&quot;,sans-serif;color:rgb(31,73,125)">Regards,<u></u><u></u></span></i></p>
<p class="MsoNormal"><i><span style="font-family:&quot;Calibri Light&quot;,sans-serif;color:rgb(31,73,125)">Zhaoyan Chen<u></u><u></u></span></i></p>
<p class="MsoNormal"><span style="font-family:&quot;Calibri Light&quot;,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<div style="border-color:currentcolor currentcolor currentcolor blue;border-style:none none none solid;border-width:medium medium medium 1.5pt;padding:0in 0in 0in 4pt">
<div>
<div style="border-color:rgb(225,225,225) currentcolor currentcolor;border-style:solid none none;border-width:1pt medium medium;padding:3pt 0in 0in">
<p class="MsoNormal"><b>From:</b> Lincoln Lavoie &lt;<a href="mailto:lylavoie@iol.unh.edu" target="_blank">lylavoie@iol.unh.edu</a>&gt; <br>
<b>Sent:</b> Friday, January 24, 2020 4:29 AM<br>
<b>To:</b> Jeremy Plsek &lt;<a href="mailto:jplsek@iol.unh.edu" target="_blank">jplsek@iol.unh.edu</a>&gt;<br>
<b>Cc:</b> Thomas Monjalon &lt;<a href="mailto:thomas@monjalon.net" target="_blank">thomas@monjalon.net</a>&gt;; <a href="mailto:ci@dpdk.org" target="_blank">ci@dpdk.org</a>; Tu, Lijuan &lt;<a href="mailto:lijuan.tu@intel.com" target="_blank">lijuan.tu@intel.com</a>&gt;; Chen, Zhaoyan &lt;<a href="mailto:zhaoyan.chen@intel.com" target="_blank">zhaoyan.chen@intel.com</a>&gt;; Xu, Qian Q &lt;<a href="mailto:qian.q.xu@intel.com" target="_blank">qian.q.xu@intel.com</a>&gt;<br>
<b>Subject:</b> Re: [dpdk-ci] Intel performance test is failing<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12pt">In the &quot;off cases,&quot; is that specific to that hardware, or does it happen on all hardware variants from time-to-time?<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Thu, Jan 23, 2020 at 11:25 AM Jeremy Plsek &lt;<a href="mailto:jplsek@iol.unh.edu" target="_blank">jplsek@iol.unh.edu</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style="border-color:currentcolor currentcolor currentcolor rgb(204,204,204);border-style:none none none solid;border-width:medium medium medium 1pt;padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">On Thu, Jan 23, 2020 at 11:06 AM Thomas Monjalon &lt;<a href="mailto:thomas@monjalon.net" target="_blank">thomas@monjalon.net</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi,<br>
&gt;<br>
&gt; The test iol-intel-Performance is failing on all patches<br>
&gt; for a couple of days.<br>
&gt; It seems to be due to a perf drop with a 10G device<br>
&gt;<br>
&gt; Can we disable this test until we understand what happens?<br>
&gt;<br>
&gt; We need also to understand how to avoid such failure,<br>
&gt; and how to monitor and disable it faster.<br>
&gt;<br>
&gt; Thanks<br>
&gt;<br>
&gt;<br>
Hi Thomas,<br>
<br>
I&#39;ve disabled it for now until someone from the Intel team can look<br>
into it (cc&#39;d).<br>
<br>
I&#39;ve also seem problems where the results are completely off<br>
(-15mpps), and I&#39;ve been rerunning those when they happen. I&#39;m hoping<br>
those can be resolved too.<br>
<br>
--<br>
Jeremy Plsek<br>
UNH InterOperability Laboratory<u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal"><br clear="all">
<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal">-- <u></u><u></u></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><b>Lincoln Lavoie</b><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Senior Engineer, Broadband Technologies<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">21 Madbury Rd., Ste. 100, Durham, NH 03824<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><a href="mailto:lylavoie@iol.unh.edu" target="_blank">lylavoie@iol.unh.edu</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><a href="https://www.iol.unh.edu" target="_blank">https://www.iol.unh.edu</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">+1-603-674-2755 (m)<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><a href="https://www.iol.unh.edu/" target="_blank"><span style="text-decoration:none"><img id="gmail-m_-5920278011901207711_x0000_i1025" src="http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/unh-iol-logo.png" border="0"></span></a><u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>

</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div></div>Jeremy Plsek<br></div><div>UNH InterOperability Laboratory<br></div></div></div></div></div></div></div></div></div></div>

  reply index

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 [this message]
2020-02-03  3:57         ` Chen, Zhaoyan
2020-03-03  9:21           ` David Marchand
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 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=CA+xUZB7CORnkzAZR_x9uN43AfJHwzvgpF66F0WdiQ+t3PdC7AA@mail.gmail.com \
    --to=jplsek@iol.unh.edu \
    --cc=ci@dpdk.org \
    --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