From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id CBE02201 for ; Wed, 7 Nov 2018 11:01:22 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Nov 2018 02:01:21 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,475,1534834800"; d="scan'208";a="90114337" Received: from irsmsx109.ger.corp.intel.com ([163.33.3.23]) by orsmga008.jf.intel.com with ESMTP; 07 Nov 2018 02:01:20 -0800 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.101]) by IRSMSX109.ger.corp.intel.com ([169.254.13.38]) with mapi id 14.03.0415.000; Wed, 7 Nov 2018 10:01:19 +0000 From: "O'Driscoll, Tim" To: "Tu, Lijuan" , "'ci@dpdk.org'" Thread-Topic: Minutes of DPDK Lab Meeting, November 6th Thread-Index: AdR144F42UUpQXW6TrGKhA/TD90q0AAdelXAAAiviAA= Date: Wed, 7 Nov 2018 10:01:19 +0000 Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAB77AD330@IRSMSX108.ger.corp.intel.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BAB77AC982@IRSMSX108.ger.corp.intel.com> <8CE3E05A3F976642AAB0F4675D0AD20E0B9B970A@SHSMSX101.ccr.corp.intel.com> In-Reply-To: <8CE3E05A3F976642AAB0F4675D0AD20E0B9B970A@SHSMSX101.ccr.corp.intel.com> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiM2NiOTg2ZDgtYWIzOC00ZDA1LThjMjQtNjZmNjZlYzdiNjQ2IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiTStpMm1FeVV0S2J5NDlKd1JVQ29sVDY1dHQrNmhjRXpYMGtBVzZzWFVMQmQxQlVZbk9LbTFpcVwvaXZkZ0lNRUUifQ== x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-ci] Minutes of DPDK Lab Meeting, November 6th 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: Wed, 07 Nov 2018 10:01:23 -0000 Great idea. Since http://core.dpdk.org/perf-lab/ is part of the core site, = it needs a patch to update it. Is there somebody who can do that? > -----Original Message----- > From: Tu, Lijuan > Sent: Wednesday, November 7, 2018 5:29 AM > To: O'Driscoll, Tim ; 'ci@dpdk.org' > > Subject: RE: Minutes of DPDK Lab Meeting, November 6th >=20 > Glad to see that the performance results public. > Can we have a portal for dashboard in dpdk.org? Currently we must know > the accurate address and we can get to the dashboard: > https://lab.dpdk.org/results/dashboard/ > It's helpful if there is an icon in http://core.dpdk.org/perf-lab/, and > we can get to the dashboard just clicking the icon, it's more > convenience. >=20 > > -----Original Message----- > > From: ci [mailto:ci-bounces@dpdk.org] On Behalf Of O'Driscoll, Tim > > Sent: Tuesday, November 6, 2018 11:19 PM > > To: 'ci@dpdk.org' > > Subject: [dpdk-ci] Minutes of DPDK Lab Meeting, November 6th > > > > Dashboard Status: > > - Jeremy is working on setting up the GA performance testing (compare > > patch performance versus previous GA release as well as with master), > and > > other dashboard features. > > - There are fewer apply errors now. This is mostly because master is > more up > > to date now because of the stage 18.11 is at. We need to monitor this > to see > > if issues occur again during the 19.02 release cycle. The Maintainers > have > > been aiming to have sub-trees merged every week, but that's never > > happened. Jeremy has also made an update to fix the exclusion of the > docs > > directory, so we're no longer seeing apply errors because of > documentation > > issues. > > > > Public Results: > > - Mellanox test configuration details have been provided to UNH and > linked > > from the results page. > > - Mellanox legal disclaimers have been provided to UNH and added to > the > > test results page. > > - Agreed that we're all happy to make the relative performance results > public. > > Jeremy will make this change and notify ci@dpdk.org when this is > complete. > > > > Patchwork Integration: > > - To make the results more visible, and to ensure that developers and > > maintainers act on them, we agreed that results should be integrated > into > > Patchwork, similar to the way that build tests are handled. Jeremy > will > > review the scripts in the ci repository to determine required email > format etc. > > Ali can help with any issues. > > > > DPDK Summit: > > - Jeremy's talk was accepted. This will cover the latest dashboard > status > > (including public relative performance results), and performance > > measurements over time. Abstract for the presentation is: > > "The DPDK Open Lab is a performance based continuous integration > system, > > supported by the DPDK project. When a patch is submitted, it is > > automatically sent to our CI to be applied and built. Once the patch > is > > compiled and installed, it is ran against each of the bare metal > environments > > hosted in the lab. This is to check for performance degradations or > speed ups > > within DPDK on various hardware platforms. This talk will explore how > the > > this system supports the development community, such as accepting > patches > > based on performance and tracking how performance has changed in DPDK > > over time. We will go over how to navigate and use the Dashboard. We > will > > show how the performance has changed in DPDK over the past six months, > > looking at relative numbers and graphs of various platforms. Finally, > we will > > also talk about the future of the Open Lab, such as running more test > cases, > > running unit tests for DPDK, additional capabilities for the > dashboard, and > > making the systems more accessible to the development community." > > > >