DPDK CI discussions
 help / color / Atom feed
* [dpdk-ci] Question about performance test
@ 2019-01-04 10:45 Rami Rosen
  2019-01-04 14:44 ` Jeremy Plsek
  0 siblings, 1 reply; 9+ messages in thread
From: Rami Rosen @ 2019-01-04 10:45 UTC (permalink / raw)
  To: ci

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

Hi,
I have a question about DPDK CI process and the tests done when a patch is
submitted to dpdk-dev mailing list.
In DPDK patch work I see these response messages from the DPDK CI for all
patches:

...
ci/intel-Performance-Testing success Performance Testing PASS
ci/mellanox-Performance-Testing success Performance Testing PASS
...

My question is (I hope and believe the info is available publicly) : which
tests are run in the ci, generating these messages?  is it done with IXIA
and DTS ? (DPDK test suite, https://doc.dpdk.org/dts/gsg/) ? are these
l2fwd/l3fwd performance tests? or more than that ? and on which
Intel/Mellanox nics ?  Are these merely performance tests, or also
functional tests ?

And BTW, I noticed that the CI runs a full performance cycle also for doc
patches (at least these messages are generated), which is a kind of
redundant (unless there is some filter which checks that if a patch only
affects modules under "doc", than such a cycle is not done but the messages
are still sent)

Regards,
Rami Rosen

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

<div dir="ltr"><div dir="ltr"><div dir="ltr">Hi,<div>I have a question about DPDK CI process and the tests done when a patch is submitted to dpdk-dev mailing list.</div><div>In DPDK patch work I see these response messages from the DPDK CI for all patches:</div><div><br></div><div>...</div><div><div><div><font color="#333333" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span style="font-size:14px">ci/intel-Performance-Testing<span style="white-space:pre">	</span>success<span style="white-space:pre">	</span>Performance Testing PASS</span></font></div><div><font color="#333333" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span style="font-size:14px">ci/mellanox-Performance-Testing<span style="white-space:pre">	</span>success<span style="white-space:pre">	</span>Performance Testing PASS </span></font></div></div><div><font color="#333333" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span style="font-size:14px">...</span></font></div><div><font color="#333333" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span style="font-size:14px"><br></span></font></div><div><font color="#333333" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span style="font-size:14px">My question is (I hope and believe the info is available publicly) : which tests are run in the ci, generating these messages?  is it done with IXIA and DTS ? (DPDK test suite, <a href="https://doc.dpdk.org/dts/gsg/">https://doc.dpdk.org/dts/gsg/</a>) ? are these l2fwd/l3fwd performance tests? or more than that ? and on which Intel/Mellanox nics ? </span></font><span style="font-size:14px;color:rgb(51,51,51);font-family:&quot;Helvetica Neue&quot;,Helvetica,Arial,sans-serif"> Are these merely performance tests, or also </span></div><div><font color="#333333" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span style="font-size:14px">functional tests ? </span></font></div><div><span style="font-size:14px;color:rgb(51,51,51);font-family:&quot;Helvetica Neue&quot;,Helvetica,Arial,sans-serif"><br></span></div><div><font color="#333333" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span style="font-size:14px">And BTW, I noticed that the CI runs a full performance cycle also for doc patches (at least these messages are generated), which is a kind of redundant (unless there is some filter which checks that if a patch only affects modules under &quot;doc&quot;, than such a cycle is not done but the messages are still sent)<br></span></font></div><div><br></div><div dir="ltr" class="gmail_signature"><div dir="ltr">Regards,<br><div>Rami Rosen<br></div></div></div></div></div></div></div>

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [dpdk-ci] Question about performance test
  2019-01-04 10:45 [dpdk-ci] Question about performance test Rami Rosen
@ 2019-01-04 14:44 ` Jeremy Plsek
  2019-01-04 15:33   ` Rami Rosen
                     ` (2 more replies)
  0 siblings, 3 replies; 9+ messages in thread
From: Jeremy Plsek @ 2019-01-04 14:44 UTC (permalink / raw)
  To: Rami Rosen; +Cc: ci

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

Hi Rami,

I'm the current maintainer of the DPDK Performance CI. I realize that the
performance results don't point to the website, so it's not obvious on
where to find this information. You can find an overview of these tests
here: https://lab.dpdk.org

Most of this information can be either found on the detailed results of a
test (such as https://lab.dpdk.org/results/dashboard/patchsets/4157/) or on
the about page (https://lab.dpdk.org/results/dashboard/about/).

But to answer your questions:
At the moment, we only run performance tests. Specifically the
nic_single_core_perf_test from the DPDK Test Suite with the TRex traffic
generator.
The devices we are testing are currently the Intel 82599ES 10G, the Intel
XL710-QDA2 40G, the Mellanox ConnectX-5 100G, and the ConnectX-4 Lx 25G and
40G.

We don't apply the doc folder when applying the series, in case a patch
included code unrelated to documentation. If others in the group feel that
it's still unnecessary to include "doc" labeled series, I can look into
filtering them out.

Thanks.


On Fri, Jan 4, 2019 at 5:46 AM Rami Rosen <ramirose@gmail.com> wrote:

> Hi,
> I have a question about DPDK CI process and the tests done when a patch is
> submitted to dpdk-dev mailing list.
> In DPDK patch work I see these response messages from the DPDK CI for all
> patches:
>
> ...
> ci/intel-Performance-Testing success Performance Testing PASS
> ci/mellanox-Performance-Testing success Performance Testing PASS
> ...
>
> My question is (I hope and believe the info is available publicly) : which
> tests are run in the ci, generating these messages?  is it done with IXIA
> and DTS ? (DPDK test suite, https://doc.dpdk.org/dts/gsg/) ? are these
> l2fwd/l3fwd performance tests? or more than that ? and on which
> Intel/Mellanox nics ?  Are these merely performance tests, or also
> functional tests ?
>
> And BTW, I noticed that the CI runs a full performance cycle also for doc
> patches (at least these messages are generated), which is a kind of
> redundant (unless there is some filter which checks that if a patch only
> affects modules under "doc", than such a cycle is not done but the messages
> are still sent)
>
> Regards,
> Rami Rosen
>


-- 
Jeremy Plsek
UNH InterOperability Laboratory

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

<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Hi Rami,</div><div><br></div><div>I&#39;m the current maintainer of the DPDK Performance CI. I realize that the performance results don&#39;t point to the website, so it&#39;s not obvious on where to find this information. You can find an overview of these tests here: <a href="https://lab.dpdk.org">https://lab.dpdk.org</a></div><div><br></div><div>Most of this information can be either found on the detailed results of a test (such as <a href="https://lab.dpdk.org/results/dashboard/patchsets/4157/">https://lab.dpdk.org/results/dashboard/patchsets/4157/</a>) or on the about page (<a href="https://lab.dpdk.org/results/dashboard/about/">https://lab.dpdk.org/results/dashboard/about/</a>).</div><div><br></div><div>But to answer your questions:</div><div>At the moment, we only run performance tests. Specifically the nic_single_core_perf_test from the DPDK Test Suite with the TRex traffic generator.</div><div>The devices we are testing are currently the Intel 82599ES 10G, the Intel XL710-QDA2 40G, the Mellanox ConnectX-5 100G, and the ConnectX-4 Lx 25G and 40G.</div><div><br></div><div>We don&#39;t apply the doc folder when applying the series, in case a patch included code unrelated to documentation. If others in the group feel that it&#39;s still unnecessary to include &quot;doc&quot; labeled series, I can look into filtering them out.</div><div><br></div><div>Thanks.<br></div><div><br></div></div></div></div></div></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Jan 4, 2019 at 5:46 AM Rami Rosen &lt;<a href="mailto:ramirose@gmail.com">ramirose@gmail.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 dir="ltr"><div dir="ltr"><div dir="ltr">Hi,<div>I have a question about DPDK CI process and the tests done when a patch is submitted to dpdk-dev mailing list.</div><div>In DPDK patch work I see these response messages from the DPDK CI for all patches:</div><div><br></div><div>...</div><div><div><div><font face="Helvetica Neue, Helvetica, Arial, sans-serif" color="#333333"><span style="font-size:14px">ci/intel-Performance-Testing<span style="white-space:pre-wrap">	</span>success<span style="white-space:pre-wrap">	</span>Performance Testing PASS</span></font></div><div><font face="Helvetica Neue, Helvetica, Arial, sans-serif" color="#333333"><span style="font-size:14px">ci/mellanox-Performance-Testing<span style="white-space:pre-wrap">	</span>success<span style="white-space:pre-wrap">	</span>Performance Testing PASS </span></font></div></div><div><font face="Helvetica Neue, Helvetica, Arial, sans-serif" color="#333333"><span style="font-size:14px">...</span></font></div><div><font face="Helvetica Neue, Helvetica, Arial, sans-serif" color="#333333"><span style="font-size:14px"><br></span></font></div><div><font face="Helvetica Neue, Helvetica, Arial, sans-serif" color="#333333"><span style="font-size:14px">My question is (I hope and believe the info is available publicly) : which tests are run in the ci, generating these messages?  is it done with IXIA and DTS ? (DPDK test suite, <a href="https://doc.dpdk.org/dts/gsg/" target="_blank">https://doc.dpdk.org/dts/gsg/</a>) ? are these l2fwd/l3fwd performance tests? or more than that ? and on which Intel/Mellanox nics ? </span></font><span style="font-size:14px;color:rgb(51,51,51);font-family:&quot;Helvetica Neue&quot;,Helvetica,Arial,sans-serif"> Are these merely performance tests, or also </span></div><div><font face="Helvetica Neue, Helvetica, Arial, sans-serif" color="#333333"><span style="font-size:14px">functional tests ? </span></font></div><div><span style="font-size:14px;color:rgb(51,51,51);font-family:&quot;Helvetica Neue&quot;,Helvetica,Arial,sans-serif"><br></span></div><div><font face="Helvetica Neue, Helvetica, Arial, sans-serif" color="#333333"><span style="font-size:14px">And BTW, I noticed that the CI runs a full performance cycle also for doc patches (at least these messages are generated), which is a kind of redundant (unless there is some filter which checks that if a patch only affects modules under &quot;doc&quot;, than such a cycle is not done but the messages are still sent)<br></span></font></div><div><br></div><div dir="ltr" class="gmail-m_-6386449682181207695gmail_signature"><div dir="ltr">Regards,<br><div>Rami Rosen<br></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>

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [dpdk-ci] Question about performance test
  2019-01-04 14:44 ` Jeremy Plsek
@ 2019-01-04 15:33   ` Rami Rosen
  2019-01-04 15:34   ` Thomas Monjalon
  2019-01-08  6:40   ` Rami Rosen
  2 siblings, 0 replies; 9+ messages in thread
From: Rami Rosen @ 2019-01-04 15:33 UTC (permalink / raw)
  To: Jeremy Plsek; +Cc: ci

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

Hi Jeremy,


Thanks for your quick reply, it fully clarifies the query I had posted.

I do not see the actual results of the DTS perf test in the links you
posted, only percentage of degradation or improvement, unless I miss
something. I believe it can be helpful if the baseline of the actual
results will also be shown
to enable comparing to other vendors besides Intel and Mellanox.

Regards,
Rami Rosen





בתאריך יום ו׳, 4 בינו׳ 2019, 16:44, מאת Jeremy Plsek <jplsek@iol.unh.edu>:

> Hi Rami,
>
> I'm the current maintainer of the DPDK Performance CI. I realize that the
> performance results don't point to the website, so it's not obvious on
> where to find this information. You can find an overview of these tests
> here: https://lab.dpdk.org
>
> Most of this information can be either found on the detailed results of a
> test (such as https://lab.dpdk.org/results/dashboard/patchsets/4157/) or
> on the about page (https://lab.dpdk.org/results/dashboard/about/).
>
> But to answer your questions:
> At the moment, we only run performance tests. Specifically the
> nic_single_core_perf_test from the DPDK Test Suite with the TRex traffic
> generator.
> The devices we are testing are currently the Intel 82599ES 10G, the Intel
> XL710-QDA2 40G, the Mellanox ConnectX-5 100G, and the ConnectX-4 Lx 25G and
> 40G.
>
> We don't apply the doc folder when applying the series, in case a patch
> included code unrelated to documentation. If others in the group feel that
> it's still unnecessary to include "doc" labeled series, I can look into
> filtering them out.
>
> Thanks.
>
>
> On Fri, Jan 4, 2019 at 5:46 AM Rami Rosen <ramirose@gmail.com> wrote:
>
>> Hi,
>> I have a question about DPDK CI process and the tests done when a patch
>> is submitted to dpdk-dev mailing list.
>> In DPDK patch work I see these response messages from the DPDK CI for all
>> patches:
>>
>> ...
>> ci/intel-Performance-Testing success Performance Testing PASS
>> ci/mellanox-Performance-Testing success Performance Testing PASS
>> ...
>>
>> My question is (I hope and believe the info is available publicly) :
>> which tests are run in the ci, generating these messages?  is it done with
>> IXIA and DTS ? (DPDK test suite, https://doc.dpdk.org/dts/gsg/) ? are
>> these l2fwd/l3fwd performance tests? or more than that ? and on which
>> Intel/Mellanox nics ?  Are these merely performance tests, or also
>> functional tests ?
>>
>> And BTW, I noticed that the CI runs a full performance cycle also for doc
>> patches (at least these messages are generated), which is a kind of
>> redundant (unless there is some filter which checks that if a patch only
>> affects modules under "doc", than such a cycle is not done but the messages
>> are still sent)
>>
>> Regards,
>> Rami Rosen
>>
>
>
> --
> Jeremy Plsek
> UNH InterOperability Laboratory
>
>

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

<div dir="auto">Hi Jeremy,<div dir="auto"><br></div><div dir="auto"><div dir="auto"><br></div><div dir="auto">Thanks for your quick reply, it fully clarifies the query I had posted.</div><div dir="auto"><br></div><div dir="auto">I do not see the actual results of the DTS perf test in the links you posted, only percentage of degradation or improvement, unless I miss something. I believe it can be helpful if the baseline of the actual results will also be shown </div><div dir="auto">to enable comparing to other vendors besides Intel and Mellanox.</div><div dir="auto"><br></div><div dir="auto">Regards,</div><div dir="auto">Rami Rosen</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div></div><br><br><div class="gmail_quote" dir="auto"><div dir="ltr">בתאריך יום ו׳, 4 בינו׳ 2019, 16:44, מאת Jeremy Plsek &lt;<a href="mailto:jplsek@iol.unh.edu">jplsek@iol.unh.edu</a>&gt;:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Hi Rami,</div><div><br></div><div>I&#39;m the current maintainer of the DPDK Performance CI. I realize that the performance results don&#39;t point to the website, so it&#39;s not obvious on where to find this information. You can find an overview of these tests here: <a href="https://lab.dpdk.org" target="_blank" rel="noreferrer">https://lab.dpdk.org</a></div><div><br></div><div>Most of this information can be either found on the detailed results of a test (such as <a href="https://lab.dpdk.org/results/dashboard/patchsets/4157/" target="_blank" rel="noreferrer">https://lab.dpdk.org/results/dashboard/patchsets/4157/</a>) or on the about page (<a href="https://lab.dpdk.org/results/dashboard/about/" target="_blank" rel="noreferrer">https://lab.dpdk.org/results/dashboard/about/</a>).</div><div><br></div><div>But to answer your questions:</div><div>At the moment, we only run performance tests. Specifically the nic_single_core_perf_test from the DPDK Test Suite with the TRex traffic generator.</div><div>The devices we are testing are currently the Intel 82599ES 10G, the Intel XL710-QDA2 40G, the Mellanox ConnectX-5 100G, and the ConnectX-4 Lx 25G and 40G.</div><div><br></div><div>We don&#39;t apply the doc folder when applying the series, in case a patch included code unrelated to documentation. If others in the group feel that it&#39;s still unnecessary to include &quot;doc&quot; labeled series, I can look into filtering them out.</div><div><br></div><div>Thanks.<br></div><div><br></div></div></div></div></div></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Jan 4, 2019 at 5:46 AM Rami Rosen &lt;<a href="mailto:ramirose@gmail.com" target="_blank" rel="noreferrer">ramirose@gmail.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 dir="ltr"><div dir="ltr"><div dir="ltr">Hi,<div>I have a question about DPDK CI process and the tests done when a patch is submitted to dpdk-dev mailing list.</div><div>In DPDK patch work I see these response messages from the DPDK CI for all patches:</div><div><br></div><div>...</div><div><div><div><font face="Helvetica Neue, Helvetica, Arial, sans-serif" color="#333333"><span style="font-size:14px">ci/intel-Performance-Testing<span style="white-space:pre-wrap">	</span>success<span style="white-space:pre-wrap">	</span>Performance Testing PASS</span></font></div><div><font face="Helvetica Neue, Helvetica, Arial, sans-serif" color="#333333"><span style="font-size:14px">ci/mellanox-Performance-Testing<span style="white-space:pre-wrap">	</span>success<span style="white-space:pre-wrap">	</span>Performance Testing PASS </span></font></div></div><div><font face="Helvetica Neue, Helvetica, Arial, sans-serif" color="#333333"><span style="font-size:14px">...</span></font></div><div><font face="Helvetica Neue, Helvetica, Arial, sans-serif" color="#333333"><span style="font-size:14px"><br></span></font></div><div><font face="Helvetica Neue, Helvetica, Arial, sans-serif" color="#333333"><span style="font-size:14px">My question is (I hope and believe the info is available publicly) : which tests are run in the ci, generating these messages?  is it done with IXIA and DTS ? (DPDK test suite, <a href="https://doc.dpdk.org/dts/gsg/" target="_blank" rel="noreferrer">https://doc.dpdk.org/dts/gsg/</a>) ? are these l2fwd/l3fwd performance tests? or more than that ? and on which Intel/Mellanox nics ? </span></font><span style="font-size:14px;color:rgb(51,51,51);font-family:&quot;Helvetica Neue&quot;,Helvetica,Arial,sans-serif"> Are these merely performance tests, or also </span></div><div><font face="Helvetica Neue, Helvetica, Arial, sans-serif" color="#333333"><span style="font-size:14px">functional tests ? </span></font></div><div><span style="font-size:14px;color:rgb(51,51,51);font-family:&quot;Helvetica Neue&quot;,Helvetica,Arial,sans-serif"><br></span></div><div><font face="Helvetica Neue, Helvetica, Arial, sans-serif" color="#333333"><span style="font-size:14px">And BTW, I noticed that the CI runs a full performance cycle also for doc patches (at least these messages are generated), which is a kind of redundant (unless there is some filter which checks that if a patch only affects modules under &quot;doc&quot;, than such a cycle is not done but the messages are still sent)<br></span></font></div><div><br></div><div dir="ltr" class="m_8710140823469032295gmail-m_-6386449682181207695gmail_signature"><div dir="ltr">Regards,<br><div>Rami Rosen<br></div></div></div></div></div></div></div>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="m_8710140823469032295gmail_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><br></div></div></div></div></div></div></div></div></div></div>
</blockquote></div></div>

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [dpdk-ci] Question about performance test
  2019-01-04 14:44 ` Jeremy Plsek
  2019-01-04 15:33   ` Rami Rosen
@ 2019-01-04 15:34   ` Thomas Monjalon
  2019-01-04 16:15     ` Jeremy Plsek
  2019-01-08  6:40   ` Rami Rosen
  2 siblings, 1 reply; 9+ messages in thread
From: Thomas Monjalon @ 2019-01-04 15:34 UTC (permalink / raw)
  To: Jeremy Plsek; +Cc: ci, Rami Rosen

04/01/2019 15:44, Jeremy Plsek:
> Hi Rami,
> 
> I'm the current maintainer of the DPDK Performance CI. I realize that the
> performance results don't point to the website, so it's not obvious on
> where to find this information. You can find an overview of these tests
> here: https://lab.dpdk.org
> 
> Most of this information can be either found on the detailed results of a
> test (such as https://lab.dpdk.org/results/dashboard/patchsets/4157/) or on
> the about page (https://lab.dpdk.org/results/dashboard/about/).

Do you plan to add such URL in the report sent to patchwork?

> We don't apply the doc folder when applying the series, in case a patch
> included code unrelated to documentation. If others in the group feel that
> it's still unnecessary to include "doc" labeled series, I can look into
> filtering them out.

Instead of filtering based on the label, you could filter based on
the paths of modified files.
Note that such filter depends on the test you run,
because you could also test the doc syntax in the CI.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [dpdk-ci] Question about performance test
  2019-01-04 15:34   ` Thomas Monjalon
@ 2019-01-04 16:15     ` Jeremy Plsek
  2019-01-04 16:19       ` Thomas Monjalon
  0 siblings, 1 reply; 9+ messages in thread
From: Jeremy Plsek @ 2019-01-04 16:15 UTC (permalink / raw)
  To: Thomas Monjalon, Rami Rosen; +Cc: ci

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

>
> I do not see the actual results of the DTS perf test in the links you
> posted, only percentage of degradation or improvement, unless I miss
> something.
>

This was done on purpose as requested by the Members participating in the
effort. This CI is meant for the DPDK maintainers to make sure that a patch
does not introduce significant performance regressions on various hardware
platforms, or to show how a patch may improve the performance of DPDK on
these platforms (such as driver updates or something in the core of DPDK
itself). It is not to compare the performance between different devices.

I believe it can be helpful if the baseline of the actual results will also
> be shown
> to enable comparing to other vendors besides Intel and Mellanox.
>

There is not a single baseline for all devices. The baselines are generated
per device. Knowing the baseline would allow creating an absolute result,
which we are trying to avoid.

Do you plan to add such URL in the report sent to patchwork?
>

Created a ticket to add the URL to the emailed reports:
https://bugs.dpdk.org/show_bug.cgi?id=180

Instead of filtering based on the label, you could filter based on
> the paths of modified files.
> Note that such filter depends on the test you run,
> because you could also test the doc syntax in the CI.
>

Okay, so if a series only modified the doc folder, then don't include it
for performance tests. Later on, we can introduce syntax checking for
documentation when we introduce more unit testing / functional testing.
https://bugs.dpdk.org/show_bug.cgi?id=181

On Fri, Jan 4, 2019 at 10:34 AM Thomas Monjalon <thomas@monjalon.net> wrote:

> 04/01/2019 15:44, Jeremy Plsek:
> > Hi Rami,
> >
> > I'm the current maintainer of the DPDK Performance CI. I realize that the
> > performance results don't point to the website, so it's not obvious on
> > where to find this information. You can find an overview of these tests
> > here: https://lab.dpdk.org
> >
> > Most of this information can be either found on the detailed results of a
> > test (such as https://lab.dpdk.org/results/dashboard/patchsets/4157/)
> or on
> > the about page (https://lab.dpdk.org/results/dashboard/about/).
>
> Do you plan to add such URL in the report sent to patchwork?
>
> > We don't apply the doc folder when applying the series, in case a patch
> > included code unrelated to documentation. If others in the group feel
> that
> > it's still unnecessary to include "doc" labeled series, I can look into
> > filtering them out.
>
> Instead of filtering based on the label, you could filter based on
> the paths of modified files.
> Note that such filter depends on the test you run,
> because you could also test the doc syntax in the CI.
>
>
>

-- 
Jeremy Plsek
UNH InterOperability Laboratory

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

<div dir="ltr"><div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>I do not see the actual results of the DTS perf test in the links you 
posted, only percentage of degradation or improvement, unless I miss 
something.</div></blockquote><div><br></div><div>This was done on purpose as requested by the Members participating in the effort. This CI is meant for the DPDK maintainers to make sure that a patch does not introduce significant performance regressions on various hardware platforms, or to show how a patch may improve the performance of DPDK on these platforms (such as driver updates or something in the core of DPDK itself). It is not to compare the performance between different devices.<br></div><div><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> I believe it can be helpful if the baseline of the actual results will also be shown <div dir="auto">to enable comparing to other vendors besides Intel and Mellanox.</div></div></blockquote><div><br></div><div>There is not a single baseline for all devices. The baselines are generated per device. Knowing the baseline would allow creating an absolute result, which we are trying to avoid.<br></div><div><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">Do you plan to add such URL in the report sent to patchwork?<span class="m_1793572375996440537gmail-m_4722669703508491933gmail-im"><br></span></div></blockquote><div dir="ltr"><span class="m_1793572375996440537gmail-m_4722669703508491933gmail-im"><br></span></div><div dir="ltr">Created a ticket to add the URL to the emailed reports: <a href="https://bugs.dpdk.org/show_bug.cgi?id=180" target="_blank">https://bugs.dpdk.org/show_bug.cgi?id=180</a></div><div dir="ltr"><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">Instead of filtering based on the label, you could filter based on<br>
the paths of modified files.<br>
Note that such filter depends on the test you run,<br>
because you could also test the doc syntax in the CI.</div></blockquote><div><br></div><div>Okay, so if a series only modified the doc folder, then don&#39;t include it for performance tests. Later on, we can introduce syntax checking for documentation when we introduce more unit testing / functional testing. <a href="https://bugs.dpdk.org/show_bug.cgi?id=181" target="_blank">https://bugs.dpdk.org/show_bug.cgi?id=181</a><br></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Jan 4, 2019 at 10:34 AM Thomas Monjalon &lt;<a href="mailto:thomas@monjalon.net" target="_blank">thomas@monjalon.net</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">04/01/2019 15:44, Jeremy Plsek:<br>
&gt; Hi Rami,<br>
&gt; <br>
&gt; I&#39;m the current maintainer of the DPDK Performance CI. I realize that the<br>
&gt; performance results don&#39;t point to the website, so it&#39;s not obvious on<br>
&gt; where to find this information. You can find an overview of these tests<br>
&gt; here: <a href="https://lab.dpdk.org" rel="noreferrer" target="_blank">https://lab.dpdk.org</a><br>
&gt; <br>
&gt; Most of this information can be either found on the detailed results of a<br>
&gt; test (such as <a href="https://lab.dpdk.org/results/dashboard/patchsets/4157/" rel="noreferrer" target="_blank">https://lab.dpdk.org/results/dashboard/patchsets/4157/</a>) or on<br>
&gt; the about page (<a href="https://lab.dpdk.org/results/dashboard/about/" rel="noreferrer" target="_blank">https://lab.dpdk.org/results/dashboard/about/</a>).<br>
<br>
Do you plan to add such URL in the report sent to patchwork?<br>
<br>
&gt; We don&#39;t apply the doc folder when applying the series, in case a patch<br>
&gt; included code unrelated to documentation. If others in the group feel that<br>
&gt; it&#39;s still unnecessary to include &quot;doc&quot; labeled series, I can look into<br>
&gt; filtering them out.<br>
<br>
Instead of filtering based on the label, you could filter based on<br>
the paths of modified files.<br>
Note that such filter depends on the test you run,<br>
because you could also test the doc syntax in the CI.<br>
<br>
<br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail-m_1793572375996440537gmail-m_4722669703508491933gmail_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>

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [dpdk-ci] Question about performance test
  2019-01-04 16:15     ` Jeremy Plsek
@ 2019-01-04 16:19       ` Thomas Monjalon
  0 siblings, 0 replies; 9+ messages in thread
From: Thomas Monjalon @ 2019-01-04 16:19 UTC (permalink / raw)
  To: Jeremy Plsek; +Cc: Rami Rosen, ci

04/01/2019 17:15, Jeremy Plsek:
> > Do you plan to add such URL in the report sent to patchwork?
> 
> Created a ticket to add the URL to the emailed reports:
> https://bugs.dpdk.org/show_bug.cgi?id=180
> 
> > Instead of filtering based on the label, you could filter based on
> > the paths of modified files.
> > Note that such filter depends on the test you run,
> > because you could also test the doc syntax in the CI.
> 
> Okay, so if a series only modified the doc folder, then don't include it
> for performance tests. Later on, we can introduce syntax checking for
> documentation when we introduce more unit testing / functional testing.
> https://bugs.dpdk.org/show_bug.cgi?id=181

Yes, thank you

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [dpdk-ci] Question about performance test
  2019-01-04 14:44 ` Jeremy Plsek
  2019-01-04 15:33   ` Rami Rosen
  2019-01-04 15:34   ` Thomas Monjalon
@ 2019-01-08  6:40   ` Rami Rosen
  2019-01-08  7:06     ` Tu, Lijuan
  2 siblings, 1 reply; 9+ messages in thread
From: Rami Rosen @ 2019-01-08  6:40 UTC (permalink / raw)
  To: Jeremy Plsek; +Cc: ci

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

Hi Jeremy,
>At the moment, we only run performance tests. Specifically the
nic_single_core_perf_test from the DPDK Test Suite

I had looked at the latest DTS repo from today:

git grep nic_single_core_perf_test
gives nothing.

Can you be more specific about exactly which *.py module from under "tests"
folder is used ?

Regards,
Rami Rosen

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

<div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Hi Jeremy,</div><div>&gt;At the moment, we only run performance tests. Specifically the nic_single_core_perf_test from the DPDK Test Suite </div><div><br></div><div>I had looked at the latest DTS repo from today:<br></div><div><br></div><div>git grep nic_single_core_perf_test</div><div>gives nothing.<br></div><div><br></div><div>Can you be more specific about exactly which *.py module from under &quot;tests&quot; folder is used ?</div><div><br></div><div>Regards,</div><div>Rami Rosen</div></div></div><br><div class="gmail_quote"><div dir="ltr"><br></div></div></div>

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [dpdk-ci] Question about performance test
  2019-01-08  6:40   ` Rami Rosen
@ 2019-01-08  7:06     ` Tu, Lijuan
  2019-01-08  8:23       ` Rami Rosen
  0 siblings, 1 reply; 9+ messages in thread
From: Tu, Lijuan @ 2019-01-08  7:06 UTC (permalink / raw)
  To: Rami Rosen, Jeremy Plsek; +Cc: ci

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

Hi Rami,

nic_single_core_perf_test is in the next branch of dts, so it can’t be found in the master branch.
Since next branch is to rework packet generator module to support a software packet generator called TREX.
A software packet generator is easily to set up with little resources comparing with hardware packet generator, IXIA.



From: ci [mailto:ci-bounces@dpdk.org] On Behalf Of Rami Rosen
Sent: Tuesday, January 8, 2019 2:40 PM
To: Jeremy Plsek <jplsek@iol.unh.edu>
Cc: ci@dpdk.org
Subject: Re: [dpdk-ci] Question about performance test

Hi Jeremy,
>At the moment, we only run performance tests. Specifically the nic_single_core_perf_test from the DPDK Test Suite

I had looked at the latest DTS repo from today:

git grep nic_single_core_perf_test
gives nothing.

Can you be more specific about exactly which *.py module from under "tests" folder is used ?

Regards,
Rami Rosen



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

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:SimSun;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="ZH-CN" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">Hi Rami,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">nic_single_core_perf_test is in the next branch of dts, so it can’t be found in the master branch.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Since next branch is to rework packet generator module to support a software packet generator called TREX.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">A software packet generator is easily to set up with little resources comparing with hardware packet generator, IXIA.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span lang="EN-US" style="font-size:10.5pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></a></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><a name="_____replyseparator"></a><b><span lang="EN-US" style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"> ci [mailto:ci-bounces@dpdk.org]
<b>On Behalf Of </b>Rami Rosen<br>
<b>Sent:</b> Tuesday, January 8, 2019 2:40 PM<br>
<b>To:</b> Jeremy Plsek &lt;jplsek@iol.unh.edu&gt;<br>
<b>Cc:</b> ci@dpdk.org<br>
<b>Subject:</b> Re: [dpdk-ci] Question about performance test<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">Hi Jeremy,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">&gt;At the moment, we only run performance tests. Specifically the nic_single_core_perf_test from the DPDK Test Suite&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">I had looked at the latest DTS repo from today:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">git grep nic_single_core_perf_test<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">gives nothing.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Can you be more specific about exactly which *.py module from under &quot;tests&quot; folder is used ?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Regards,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Rami Rosen<o:p></o:p></span></p>
</div>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [dpdk-ci] Question about performance test
  2019-01-08  7:06     ` Tu, Lijuan
@ 2019-01-08  8:23       ` Rami Rosen
  0 siblings, 0 replies; 9+ messages in thread
From: Rami Rosen @ 2019-01-08  8:23 UTC (permalink / raw)
  To: Tu, Lijuan; +Cc: Jeremy Plsek, ci

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

Hi Lijuan,
Thanks for the quick response, your replies clarifies everything now!

And Indeed:
git checkout next
Switched to branch 'next'

git grep nic_single_core_perf
doc/dts_gsg/trex.rst:This is supported for the ``nic_single_core_per
framework/etgen.py:        This function is set only for function se
framework/etgen.py:        Note that this function is only set for t
test_plans/nic_single_core_perf_test_plan.rst:    1) nic_single_core
test_plans/nic_single_core_perf_test_plan.rst:    3) nic_single_core
tests/TestSuite_nic_single_core_perf.py:    def test_nic_single_core

Regards,
Rami Rosen



On Tue, Jan 8, 2019 at 9:06 AM Tu, Lijuan <lijuan.tu@intel.com> wrote:

> Hi Rami,
>
>
>
> nic_single_core_perf_test is in the next branch of dts, so it can’t be
> found in the master branch.
>
> Since next branch is to rework packet generator module to support a
> software packet generator called TREX.
>
> A software packet generator is easily to set up with little resources
> comparing with hardware packet generator, IXIA.
>
>
>
>
>
>
>
> *From:* ci [mailto:ci-bounces@dpdk.org] *On Behalf Of *Rami Rosen
> *Sent:* Tuesday, January 8, 2019 2:40 PM
> *To:* Jeremy Plsek <jplsek@iol.unh.edu>
> *Cc:* ci@dpdk.org
> *Subject:* Re: [dpdk-ci] Question about performance test
>
>
>
> Hi Jeremy,
>
> >At the moment, we only run performance tests. Specifically the
> nic_single_core_perf_test from the DPDK Test Suite
>
>
>
> I had looked at the latest DTS repo from today:
>
>
>
> git grep nic_single_core_perf_test
>
> gives nothing.
>
>
>
> Can you be more specific about exactly which *.py module from under
> "tests" folder is used ?
>
>
>
> Regards,
>
> Rami Rosen
>
>
>
>
>


-- 
regards,
Rami Rosen

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

<div dir="ltr"><div dir="ltr"><div dir="ltr">Hi Lijuan,<div>Thanks for the quick response, your replies clarifies everything now!</div><div><br></div><div>And Indeed:</div><div><div>git checkout next</div><div>Switched to branch &#39;next&#39;</div></div><div><br></div><div><div>git grep nic_single_core_perf</div><div>doc/dts_gsg/trex.rst:This is supported for the ``nic_single_core_per</div><div>framework/etgen.py:        This function is set only for function se</div><div>framework/etgen.py:        Note that this function is only set for t</div><div>test_plans/nic_single_core_perf_test_plan.rst:    1) nic_single_core</div><div>test_plans/nic_single_core_perf_test_plan.rst:    3) nic_single_core</div><div>tests/TestSuite_nic_single_core_perf.py:    def test_nic_single_core</div></div><div><br></div><div>Regards,</div><div>Rami Rosen</div><div><br></div><div><br></div></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Jan 8, 2019 at 9:06 AM Tu, Lijuan &lt;<a href="mailto:lijuan.tu@intel.com">lijuan.tu@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="ZH-CN">
<div class="gmail-m_-1302790269651696504WordSection1">
<p class="MsoNormal"><span lang="EN-US">Hi Rami,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">nic_single_core_perf_test is in the next branch of dts, so it can’t be found in the master branch.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Since next branch is to rework packet generator module to support a software packet generator called TREX.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">A software packet generator is easily to set up with little resources comparing with hardware packet generator, IXIA.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><a name="m_-1302790269651696504__MailEndCompose"><span lang="EN-US" style="font-size:10.5pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></a></p>
<div style="border-top:none;border-right:none;border-bottom:none;border-left:1.5pt solid blue;padding:0cm 0cm 0cm 4pt">
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0cm 0cm">
<p class="MsoNormal"><a name="m_-1302790269651696504______replyseparator"></a><b><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif">From:</span></b><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif"> ci [mailto:<a href="mailto:ci-bounces@dpdk.org" target="_blank">ci-bounces@dpdk.org</a>]
<b>On Behalf Of </b>Rami Rosen<br>
<b>Sent:</b> Tuesday, January 8, 2019 2:40 PM<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> <a href="mailto:ci@dpdk.org" target="_blank">ci@dpdk.org</a><br>
<b>Subject:</b> Re: [dpdk-ci] Question about performance test<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">Hi Jeremy,<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">&gt;At the moment, we only run performance tests. Specifically the nic_single_core_perf_test from the DPDK Test Suite <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">I had looked at the latest DTS repo from today:<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">git grep nic_single_core_perf_test<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">gives nothing.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Can you be more specific about exactly which *.py module from under &quot;tests&quot; folder is used ?<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Regards,<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Rami Rosen<u></u><u></u></span></p>
</div>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
</div>
</div>
</div>
</div>
</div>
</div>

</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">regards,<br><div>Rami Rosen</div></div></div>

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, back to index

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-01-04 10:45 [dpdk-ci] Question about performance test Rami Rosen
2019-01-04 14:44 ` Jeremy Plsek
2019-01-04 15:33   ` Rami Rosen
2019-01-04 15:34   ` Thomas Monjalon
2019-01-04 16:15     ` Jeremy Plsek
2019-01-04 16:19       ` Thomas Monjalon
2019-01-08  6:40   ` Rami Rosen
2019-01-08  7:06     ` Tu, Lijuan
2019-01-08  8:23       ` Rami Rosen

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