From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <jlovato@linuxfoundation.org> Received: from mail-lf1-f52.google.com (mail-lf1-f52.google.com [209.85.167.52]) by dpdk.org (Postfix) with ESMTP id C19CA3238 for <ci@dpdk.org>; Thu, 15 Nov 2018 23:31:33 +0100 (CET) Received: by mail-lf1-f52.google.com with SMTP id n18so15272533lfh.6 for <ci@dpdk.org>; Thu, 15 Nov 2018 14:31:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=UiJv3ZI8hDWjWmPNgR+F56MykukUN0YSqFykMG6tvFg=; b=PgDNjyd1wtXT9WbS7wSp4JPIPyKaJBQsU0ycW/EfbB0M7ULe8jO1LsNYEo7mbXL2LS NviA/rVwkHnNJtIPZXdxoj1J0lBT0vWL7KOZ75haVrGt+vDhc+IS2Xo79K6ENhai6QOU D0z4LUKzdlkRMdy5g43e3vRz5ms8yAFoOYYhQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=UiJv3ZI8hDWjWmPNgR+F56MykukUN0YSqFykMG6tvFg=; b=OGsdQuvQ0kEo2biwkn8I4oFSylfu4FUG2SyxhO2Txh4uK7JidZkAupDa+FrJ69Q2E/ s/zakIJp4iIijsUfiJtge8xJM9L8aZ5TwPDUge/L9cGKgP/U3e997sBn12LEtGBBTWB6 TmS6qla7FYuPtBQwTKX0TioRmMAC7dvGxYLqNRHt7y7Xi+E91dkrYnNxODdAAXCtHcAF EHbPVcbEaXVtA+ldRr747fsDiXi2VtHMPhu6aAi4goCaTv9fvfWc4sNMRtbh+VoWrlal PdEqg3J43snYNu8eJm4SPMwQfM9+Fxb8WZzNvxCcDE5ADXNf8ha1RNFoGOdQDZhkazD+ S1ng== X-Gm-Message-State: AGRZ1gKQxtX8qyxx8Te1alwsi5Mpx7Yc3A+fzdk55K1WHDoY16tx1nPf AILMv9LmI70QPlm9V3tMVkTkbgXNqmO9NFARjBWjnQ== X-Google-Smtp-Source: AJdET5f6zplS5Fk9Un6mvC5iX70vMKvowXr+sNDSIsLP0zigRhruwN0mKxNUvLuZEOGRe5Crtgekkj1za+fGDMKEc94= X-Received: by 2002:ac2:4116:: with SMTP id b22mr4652685lfi.19.1542321093118; Thu, 15 Nov 2018 14:31:33 -0800 (PST) MIME-Version: 1.0 References: <CA+xUZB7n72XpMWWctwBJvu3c6ZahHttKj9J4nEp1cbGQLFEpyg@mail.gmail.com> <CA+xUZB4=Yve-z5TdCRRPCKYf_BG4bgKKGmzR=X1Rqo77ac7M4w@mail.gmail.com> <CA+xUZB63aEB4AetF0MKqRvsXf4QbPSmsWf38FgDKphvjj+1Usg@mail.gmail.com> <1654420.p2kmoy7Ngz@xps> <26FA93C7ED1EAA44AB77D62FBE1D27BAB77BA42C@IRSMSX108.ger.corp.intel.com> In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BAB77BA42C@IRSMSX108.ger.corp.intel.com> From: Jill Lovato <jlovato@linuxfoundation.org> Date: Thu, 15 Nov 2018 14:30:54 -0800 Message-ID: <CANA499Eya9Y+7evKLW4Nzz1ZuXw9j4OXjPXhG1V8yR-90ztXOQ@mail.gmail.com> To: "O'Driscoll, Tim" <tim.odriscoll@intel.com> Cc: Thomas Monjalon <thomas@monjalon.net>, jplsek@iol.unh.edu, ferruh.yigit@intel.com, ci@dpdk.org, marketing@dpdk.org, Lincoln Lavoie <lylavoie@iol.unh.edu>, pmacarth@iol.unh.edu Content-Type: multipart/alternative; boundary="000000000000e2a8e9057abb9cea" X-Mailman-Approved-At: Fri, 16 Nov 2018 11:06:53 +0100 Subject: Re: [dpdk-ci] [dpdk-marketing] Results are now public X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK CI discussions <ci.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/ci>, <mailto:ci-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/ci/> List-Post: <mailto:ci@dpdk.org> List-Help: <mailto:ci-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/ci>, <mailto:ci-request@dpdk.org?subject=subscribe> X-List-Received-Date: Thu, 15 Nov 2018 22:31:34 -0000 --000000000000e2a8e9057abb9cea Content-Type: text/plain; charset="UTF-8" Agree on the draft - thank you, Jeremy, for putting this together! I haven't seen any photos of the lab - can someone point me in the right direction, or perhaps snap and few and share on this thread? I can get this posted to the DPDK site as early as tomorrow (Friday) morning. Many thanks, Jill On Thu, Nov 15, 2018 at 2:13 PM O'Driscoll, Tim <tim.odriscoll@intel.com> wrote: > This looks good to me too. Some pictures would be nice, perhaps a snapshot > of the dashboard some of the hardware in the lab. It would be good to get > this posted on dpdk.org, and send a note to announce@dpdk.org to let > people know about it. > > > -----Original Message----- > > From: Thomas Monjalon [mailto:thomas@monjalon.net] > > Sent: Wednesday, November 14, 2018 10:17 PM > > To: Jeremy Plsek <jplsek@iol.unh.edu> > > Cc: O'Driscoll, Tim <tim.odriscoll@intel.com>; Yigit, Ferruh > > <ferruh.yigit@intel.com>; ci@dpdk.org; marketing@dpdk.org; Lincoln > > Lavoie <lylavoie@iol.unh.edu>; Patrick MacArthur <pmacarth@iol.unh.edu> > > Subject: Re: [dpdk-marketing] [dpdk-ci] Results are now public > > > > Looks great! > > I think adding pictures would be nice for the blog. > > Thank you > > > > 14/11/2018 22:07, Jeremy Plsek: > > > With help from Lincoln and Patrick, below is an initial draft of the > > blog post. > > > > > > > > > > > > DPDK Community Lab Publishes Relative Performance Testing Results > > > > > > The DPDK Community Lab is an open, independent testing resource for > > > the DPDK project. Its purpose is to perform automated testing on > > > incoming patch submissions, to ensure the performance and quality of > > > DPDK is maintained. Participation in the lab is open to all DPDK > > > project participants. > > > > > > For some time now, the DPDK Community Lab has been gathering > > > performance deltas using the single-core packet I/O layer 2 throughput > > > test from DTS for each patch series submitted to DPDK compared to the > > > master branch. We are pleased to announce that the Lab has recently > > > been allowed to make these results public. These results are also now > > > published to Patchwork as they are automatically generated. These > > > results currently contain Mellanox and Intel devices, and the lab is > > > able to support hardware from any DPDK participants wishing to support > > > these testing efforts. > > > > > > To view these results, you can go to DPDK Community Lab Dashboard via > > > the following link: https://lab.dpdk.org. The dashboard lists an > > > overview of all active patch series and their results. Detailed > > > results can be viewed by clicking on the patch series. If a patch > > > fails to merge into master, a build log will show to help identify any > > > issues. If a patch cleanly merges into master, performance delta > > > results will show for each participating member. > > > > > > The Lab is hosted by the University of New Hampshire InterOperability > > > Laboratory, as a neutral, third party location. This provides a secure > > > environment for hosting equipment and generating unbiased results for > > > all participating vendors. Lab participants, i.e. companies hosting > > > equipment in the testing, can securely access their equipment through > > > a VPN, allowing for maintenance and performance tuning, as the DPDK > > > project progresses. > > > > > > The Lab works by polling the Patchwork API. When new patches are > > > submitted, the CI server merges them with the master branch and > > > generates a tarball. Each participating system unpacks and installs > > > the DPDK tarball and then runs the performance testing against this > > > DPDK build. When all systems have finished testing, the CI gathers the > > > results into our internal database to be shown on the Dashboard, and > > > sends final reports to Patchwork to show up on the submitted patch. > > > This allows patch submitters to utilize Patchwork to view their > > > individual results, while also allowing anyone to quickly see an > > > overview of results on the Dashboard. The system provides maintainers > > > with positive confirmation of the stability and performance of the > > > overall project. > > > > > > In the future, we plan to open the Lab to more testing scenarios, such > > > as performance testing of other features, beyond single-core packet > > > I/O layer 2 throughput, and possibly running Unit Tests for DPDK. > > > Additional features will be added to the Dashboard, such as showing > > > graphs of the performance changes of master over time. > > > > > > If your company would like to be involved, email the Continuous > > > Integration group at ci@dpdk.org and dpdklab@iol.unh.edu. > > > > > > > > > > > > Thanks! > > > > > > On Fri, Nov 9, 2018 at 10:03 AM Jeremy Plsek <jplsek@iol.unh.edu> > > wrote: > > > > > > > > I can try to get it done later today, but I expect it to be more > > likely done on Monday. > > > > > > > > On Fri, Nov 9, 2018, 9:08 AM O'Driscoll, Tim > > <tim.odriscoll@intel.com wrote: > > > >> > > > >> > > > >> > > > >> > -----Original Message----- > > > >> > From: Thomas Monjalon [mailto:thomas@monjalon.net] > > > >> > Sent: Friday, November 9, 2018 2:02 PM > > > >> > To: O'Driscoll, Tim <tim.odriscoll@intel.com> > > > >> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Jeremy Plsek > > > >> > <jplsek@iol.unh.edu>; ci@dpdk.org; marketing@dpdk.org > > > >> > Subject: Re: [dpdk-marketing] [dpdk-ci] Results are now public > > > >> > > > > >> > 09/11/2018 14:58, O'Driscoll, Tim: > > > >> > > From: Thomas Monjalon > > > >> > > > 08/11/2018 14:01, Ferruh Yigit: > > > >> > > > > On 11/7/2018 7:30 AM, Thomas Monjalon wrote: > > > >> > > > > > 06/11/2018 16:33, Jeremy Plsek: > > > >> > > > > >> Hi all, > > > >> > > > > >> > > > >> > > > > >> This is just an update that all detailed results are now > > > >> > public. > > > >> > > > > >> > > > >> > > > > >> If there is anything out of place, feel free to let me > > know! > > > >> > > > > > > > > >> > > > > > It is really nice! > > > >> > > > > > Thank you > > > >> > > > > > > > >> > > > > Should we announce this in 'announce' or 'dev' mail lists? > > Many > > > >> > people > > > >> > > > not aware > > > >> > > > > of this. > > > >> > > > > > > >> > > > It deserves an announce. > > > >> > > > And even a blog post I guess. > > > >> > > > +Cc marketing team > > > >> > > > > > >> > > Agreed. I can do a quick post to announce@dpdk.org. I believe > > Jeremy > > > >> > is working on a blog post which can provide more detail. > > > >> > > > > >> > Should we wait to have a blog post and reference it in the > > announce? > > > >> > > > >> Good question. I think it depends how long the blog will take. If > > we can do it fairly quickly, then this is a good idea. If it's going to > > take a few weeks, then we should announce it now. > > > >> > > > >> Jeremy: When do you think the blog will be ready? > > > >> > > > > > > > > > -- > > > Jeremy Plsek > > > UNH InterOperability Laboratory > > > > > > > > > > > > > -- *Jill Lovato* Senior PR Manager The Linux Foundation jlovato@linuxfoundation.org Skype: jill.lovato1 Phone: +1.503.703.8268 --000000000000e2a8e9057abb9cea Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Agree on the draft - thank you, Jeremy, for putting this t= ogether!<div><br></div><div>I haven't seen any photos of the lab - can = someone point me in the right direction, or perhaps snap and few and share = on this thread? I can get this posted to the DPDK site as early as tomorrow= (Friday) morning.=C2=A0</div><div><br></div><div>Many thanks,</div><div>Ji= ll</div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Thu, Nov 15, 201= 8 at 2:13 PM O'Driscoll, Tim <<a href=3D"mailto:tim.odriscoll@intel.= com">tim.odriscoll@intel.com</a>> wrote:<br></div><blockquote class=3D"g= mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l= eft:1ex">This looks good to me too. Some pictures would be nice, perhaps a = snapshot of the dashboard some of the hardware in the lab. It would be good= to get this posted on <a href=3D"http://dpdk.org" rel=3D"noreferrer" targe= t=3D"_blank">dpdk.org</a>, and send a note to <a href=3D"mailto:announce@dp= dk.org" target=3D"_blank">announce@dpdk.org</a> to let people know about it= .<br> <br> > -----Original Message-----<br> > From: Thomas Monjalon [mailto:<a href=3D"mailto:thomas@monjalon.net" t= arget=3D"_blank">thomas@monjalon.net</a>]<br> > Sent: Wednesday, November 14, 2018 10:17 PM<br> > To: Jeremy Plsek <<a href=3D"mailto:jplsek@iol.unh.edu" target=3D"_= blank">jplsek@iol.unh.edu</a>><br> > Cc: O'Driscoll, Tim <<a href=3D"mailto:tim.odriscoll@intel.com"= target=3D"_blank">tim.odriscoll@intel.com</a>>; Yigit, Ferruh<br> > <<a href=3D"mailto:ferruh.yigit@intel.com" target=3D"_blank">ferruh= .yigit@intel.com</a>>; <a href=3D"mailto:ci@dpdk.org" target=3D"_blank">= ci@dpdk.org</a>; <a href=3D"mailto:marketing@dpdk.org" target=3D"_blank">ma= rketing@dpdk.org</a>; Lincoln<br> > Lavoie <<a href=3D"mailto:lylavoie@iol.unh.edu" target=3D"_blank">l= ylavoie@iol.unh.edu</a>>; Patrick MacArthur <<a href=3D"mailto:pmacar= th@iol.unh.edu" target=3D"_blank">pmacarth@iol.unh.edu</a>><br> > Subject: Re: [dpdk-marketing] [dpdk-ci] Results are now public<br> > <br> > Looks great!<br> > I think adding pictures would be nice for the blog.<br> > Thank you<br> > <br> > 14/11/2018 22:07, Jeremy Plsek:<br> > > With help from Lincoln and Patrick, below is an initial draft of = the<br> > blog post.<br> > ><br> > ><br> > ><br> > > DPDK Community Lab Publishes Relative Performance Testing Results= <br> > ><br> > > The DPDK Community Lab is an open, independent testing resource f= or<br> > > the DPDK project. Its purpose is to perform automated testing on<= br> > > incoming patch submissions, to ensure the performance and quality= of<br> > > DPDK is maintained. Participation in the lab is open to all DPDK<= br> > > project participants.<br> > ><br> > > For some time now, the DPDK Community Lab has been gathering<br> > > performance deltas using the single-core packet I/O layer 2 throu= ghput<br> > > test from DTS for each patch series submitted to DPDK compared to= the<br> > > master branch. We are pleased to announce that the Lab has recent= ly<br> > > been allowed to make these results public. These results are also= now<br> > > published to Patchwork as they are automatically generated. These= <br> > > results currently contain Mellanox and Intel devices, and the lab= is<br> > > able to support hardware from any DPDK participants wishing to su= pport<br> > > these testing efforts.<br> > ><br> > > To view these results, you can go to DPDK Community Lab Dashboard= via<br> > > the following link: <a href=3D"https://lab.dpdk.org" rel=3D"noref= errer" target=3D"_blank">https://lab.dpdk.org</a>. The dashboard lists an<b= r> > > overview of all active patch series and their results. Detailed<b= r> > > results can be viewed by clicking on the patch series. If a patch= <br> > > fails to merge into master, a build log will show to help identif= y any<br> > > issues. If a patch cleanly merges into master, performance delta<= br> > > results will show for each participating member.<br> > ><br> > > The Lab is hosted by the University of New Hampshire InterOperabi= lity<br> > > Laboratory, as a neutral, third party location. This provides a s= ecure<br> > > environment for hosting equipment and generating unbiased results= for<br> > > all participating vendors. Lab participants, i.e. companies hosti= ng<br> > > equipment in the testing, can securely access their equipment thr= ough<br> > > a VPN, allowing for maintenance and performance tuning, as the DP= DK<br> > > project progresses.<br> > ><br> > > The Lab works by polling the Patchwork API. When new patches are<= br> > > submitted, the CI server merges them with the master branch and<b= r> > > generates a tarball. Each participating system unpacks and instal= ls<br> > > the DPDK tarball and then runs the performance testing against th= is<br> > > DPDK build. When all systems have finished testing, the CI gather= s the<br> > > results into our internal database to be shown on the Dashboard, = and<br> > > sends final reports to Patchwork to show up on the submitted patc= h.<br> > > This allows patch submitters to utilize Patchwork to view their<b= r> > > individual results, while also allowing anyone to quickly see an<= br> > > overview of results on the Dashboard. The system provides maintai= ners<br> > > with positive confirmation of the stability and performance of th= e<br> > > overall project.<br> > ><br> > > In the future, we plan to open the Lab to more testing scenarios,= such<br> > > as performance testing of other features, beyond single-core pack= et<br> > > I/O layer 2 throughput, and possibly running Unit Tests for DPDK.= <br> > > Additional features will be added to the Dashboard, such as showi= ng<br> > > graphs of the performance changes of master over time.<br> > ><br> > > If your company would like to be involved, email the Continuous<b= r> > > Integration group at <a href=3D"mailto:ci@dpdk.org" target=3D"_bl= ank">ci@dpdk.org</a> and <a href=3D"mailto:dpdklab@iol.unh.edu" target=3D"_= blank">dpdklab@iol.unh.edu</a>.<br> > ><br> > ><br> > ><br> > > Thanks!<br> > ><br> > > On Fri, Nov 9, 2018 at 10:03 AM Jeremy Plsek <<a href=3D"mailt= o:jplsek@iol.unh.edu" target=3D"_blank">jplsek@iol.unh.edu</a>><br> > wrote:<br> > > ><br> > > > I can try to get it done later today, but I expect it to be = more<br> > likely done on Monday.<br> > > ><br> > > > On Fri, Nov 9, 2018, 9:08 AM O'Driscoll, Tim<br> > <<a href=3D"mailto:tim.odriscoll@intel.com" target=3D"_blank">tim.o= driscoll@intel.com</a> wrote:<br> > > >><br> > > >><br> > > >><br> > > >> > -----Original Message-----<br> > > >> > From: Thomas Monjalon [mailto:<a href=3D"mailto:tho= mas@monjalon.net" target=3D"_blank">thomas@monjalon.net</a>]<br> > > >> > Sent: Friday, November 9, 2018 2:02 PM<br> > > >> > To: O'Driscoll, Tim <<a href=3D"mailto:tim.o= driscoll@intel.com" target=3D"_blank">tim.odriscoll@intel.com</a>><br> > > >> > Cc: Yigit, Ferruh <<a href=3D"mailto:ferruh.yigi= t@intel.com" target=3D"_blank">ferruh.yigit@intel.com</a>>; Jeremy Plsek= <br> > > >> > <<a href=3D"mailto:jplsek@iol.unh.edu" target=3D= "_blank">jplsek@iol.unh.edu</a>>; <a href=3D"mailto:ci@dpdk.org" target= =3D"_blank">ci@dpdk.org</a>; <a href=3D"mailto:marketing@dpdk.org" target= =3D"_blank">marketing@dpdk.org</a><br> > > >> > Subject: Re: [dpdk-marketing] [dpdk-ci] Results are= now public<br> > > >> ><br> > > >> > 09/11/2018 14:58, O'Driscoll, Tim:<br> > > >> > > From: Thomas Monjalon<br> > > >> > > > 08/11/2018 14:01, Ferruh Yigit:<br> > > >> > > > > On 11/7/2018 7:30 AM, Thomas Monjalo= n wrote:<br> > > >> > > > > > 06/11/2018 16:33, Jeremy Plsek:= <br> > > >> > > > > >> Hi all,<br> > > >> > > > > >><br> > > >> > > > > >> This is just an update that= all detailed results are now<br> > > >> > public.<br> > > >> > > > > >><br> > > >> > > > > >> If there is anything out of= place, feel free to let me<br> > know!<br> > > >> > > > > ><br> > > >> > > > > > It is really nice!<br> > > >> > > > > > Thank you<br> > > >> > > > ><br> > > >> > > > > Should we announce this in 'anno= unce' or 'dev' mail lists?<br> > Many<br> > > >> > people<br> > > >> > > > not aware<br> > > >> > > > > of this.<br> > > >> > > ><br> > > >> > > > It deserves an announce.<br> > > >> > > > And even a blog post I guess.<br> > > >> > > > +Cc marketing team<br> > > >> > ><br> > > >> > > Agreed. I can do a quick post to <a href=3D"ma= ilto:announce@dpdk.org" target=3D"_blank">announce@dpdk.org</a>. I believe<= br> > Jeremy<br> > > >> > is working on a blog post which can provide more de= tail.<br> > > >> ><br> > > >> > Should we wait to have a blog post and reference it= in the<br> > announce?<br> > > >><br> > > >> Good question. I think it depends how long the blog will= take. If<br> > we can do it fairly quickly, then this is a good idea. If it's goi= ng to<br> > take a few weeks, then we should announce it now.<br> > > >><br> > > >> Jeremy: When do you think the blog will be ready?<br> > > >><br> > ><br> > ><br> > > --<br> > > Jeremy Plsek<br> > > UNH InterOperability Laboratory<br> > ><br> > <br> > <br> > <br> > <br> <br> </blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"= class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"l= tr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><font color=3D"#999999= "><strong>Jill Lovato</strong></font></div><div><font color=3D"#999999">Sen= ior PR Manager </font></div><div><font color=3D"#999999">The Linux Foundati= on</font></div><div><a href=3D"mailto:jlovato@linuxfoundation.org" target= =3D"_blank">jlovato@linuxfoundation.org</a>=C2=A0</div><div><font color=3D"= #999999">Skype: jill.lovato1</font></div><div><font color=3D"#999999">Phone= : +1.503.703.8268</font></div></div></div></div></div></div></div></div> --000000000000e2a8e9057abb9cea--