From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 3CF0C201 for ; Wed, 7 Nov 2018 06:29:11 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Nov 2018 21:29:10 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,474,1534834800"; d="scan'208";a="84569686" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by fmsmga008.fm.intel.com with ESMTP; 06 Nov 2018 21:29:10 -0800 Received: from fmsmsx153.amr.corp.intel.com (10.18.125.6) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 6 Nov 2018 21:29:10 -0800 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by FMSMSX153.amr.corp.intel.com (10.18.125.6) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 6 Nov 2018 21:29:10 -0800 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.102]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.199]) with mapi id 14.03.0415.000; Wed, 7 Nov 2018 13:29:08 +0800 From: "Tu, Lijuan" To: "O'Driscoll, Tim" , "'ci@dpdk.org'" Thread-Topic: Minutes of DPDK Lab Meeting, November 6th Thread-Index: AdR144F42UUpQXW6TrGKhA/TD90q0AAdelXA Date: Wed, 7 Nov 2018 05:29:07 +0000 Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0B9B970A@SHSMSX101.ccr.corp.intel.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BAB77AC982@IRSMSX108.ger.corp.intel.com> In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BAB77AC982@IRSMSX108.ger.corp.intel.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiM2NiOTg2ZDgtYWIzOC00ZDA1LThjMjQtNjZmNjZlYzdiNjQ2IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiTStpMm1FeVV0S2J5NDlKd1JVQ29sVDY1dHQrNmhjRXpYMGtBVzZzWFVMQmQxQlVZbk9LbTFpcVwvaXZkZ0lNRUUifQ== x-originating-ip: [10.239.127.40] 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 05:29:12 -0000 Glad to see that the performance results public.=20 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/resu= lts/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. > -----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 >=20 > 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 hav= e > 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 documentatio= n > issues. >=20 > Public Results: > - Mellanox test configuration details have been provided to UNH and linke= d > 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 pu= blic. > Jeremy will make this change and notify ci@dpdk.org when this is complete= . >=20 > 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 forma= t etc. > Ali can help with any issues. >=20 > 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 environm= ents > 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 cas= es, > running unit tests for DPDK, additional capabilities for the dashboard, a= nd > making the systems more accessible to the development community." >=20 >=20