From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 ; Thu, 15 Nov 2018 23:31:33 +0100 (CET) Received: by mail-lf1-f52.google.com with SMTP id n18so15272533lfh.6 for ; 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: <1654420.p2kmoy7Ngz@xps> <26FA93C7ED1EAA44AB77D62FBE1D27BAB77BA42C@IRSMSX108.ger.corp.intel.com> In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BAB77BA42C@IRSMSX108.ger.corp.intel.com> From: Jill Lovato Date: Thu, 15 Nov 2018 14:30:54 -0800 Message-ID: To: "O'Driscoll, Tim" Cc: Thomas Monjalon , jplsek@iol.unh.edu, ferruh.yigit@intel.com, ci@dpdk.org, marketing@dpdk.org, Lincoln Lavoie , 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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 > > Cc: O'Driscoll, Tim ; Yigit, Ferruh > > ; ci@dpdk.org; marketing@dpdk.org; Lincoln > > Lavoie ; Patrick MacArthur > > 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 > > 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 > > > > >> > > > >> > > > >> > > > >> > -----Original Message----- > > > >> > From: Thomas Monjalon [mailto:thomas@monjalon.net] > > > >> > Sent: Friday, November 9, 2018 2:02 PM > > > >> > To: O'Driscoll, Tim > > > >> > Cc: Yigit, Ferruh ; Jeremy Plsek > > > >> > ; 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
Agree on the draft - thank you, Jeremy, for putting this t= ogether!

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

Many thanks,
Ji= ll

On Thu, Nov 15, 201= 8 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; ma= rketing@dpdk.org; Lincoln
> Lavoie <l= ylavoie@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 f= or
> > the DPDK project. Its purpose is to perform automated testing on<= br> > > incoming patch submissions, to ensure the performance and quality= of
> > DPDK is maintained. Participation in the lab is open to all DPDK<= br> > > project participants.
> >
> > For some time now, the DPDK Community Lab has been gathering
> > performance deltas using the single-core packet I/O layer 2 throu= ghput
> > test from DTS for each patch series submitted to DPDK compared to= the
> > master branch. We are pleased to announce that the Lab has recent= ly
> > 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 su= pport
> > 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 identif= y any
> > issues. If a patch cleanly merges into master, performance delta<= br> > > results will show for each participating member.
> >
> > The Lab is hosted by the University of New Hampshire InterOperabi= lity
> > Laboratory, as a neutral, third party location. This provides a s= ecure
> > environment for hosting equipment and generating unbiased results= for
> > all participating vendors. Lab participants, i.e. companies hosti= ng
> > equipment in the testing, can securely access their equipment thr= ough
> > a VPN, allowing for maintenance and performance tuning, as the DP= DK
> > project progresses.
> >
> > The Lab works by polling the Patchwork API. When new patches are<= br> > > submitted, the CI server merges them with the master branch and > > generates a tarball. Each participating system unpacks and instal= ls
> > the DPDK tarball and then runs the performance testing against th= is
> > DPDK build. When all systems have finished testing, the CI gather= s the
> > results into our internal database to be shown on the Dashboard, = and
> > sends final reports to Patchwork to show up on the submitted patc= h.
> > This allows patch submitters to utilize Patchwork to view their > > individual results, while also allowing anyone to quickly see an<= br> > > overview of results on the Dashboard. The system provides maintai= ners
> > with positive confirmation of the stability and performance of th= e
> > 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 pack= et
> > I/O layer 2 throughput, and possibly running Unit Tests for DPDK.=
> > Additional features will be added to the Dashboard, such as showi= ng
> > 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.o= driscoll@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 Monjalo= n 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 'anno= unce' 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<= br> > Jeremy
> > >> > is working on a blog post which can provide more de= tail.
> > >> >
> > >> > 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 goi= ng 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
Sen= ior PR Manager
The Linux Foundati= on
Skype: jill.lovato1
Phone= : +1.503.703.8268
--000000000000e2a8e9057abb9cea--