From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id CD4992862 for ; Tue, 6 Nov 2018 16:19:11 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Nov 2018 07:19:10 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,472,1534834800"; d="scan'208";a="98057755" Received: from irsmsx101.ger.corp.intel.com ([163.33.3.153]) by orsmga003.jf.intel.com with ESMTP; 06 Nov 2018 07:19:09 -0800 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.101]) by IRSMSX101.ger.corp.intel.com ([169.254.1.134]) with mapi id 14.03.0415.000; Tue, 6 Nov 2018 15:19:09 +0000 From: "O'Driscoll, Tim" To: "'ci@dpdk.org'" Thread-Topic: Minutes of DPDK Lab Meeting, November 6th Thread-Index: AdR144F42UUpQXW6TrGKhA/TD90q0A== Date: Tue, 6 Nov 2018 15:19:08 +0000 Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAB77AC982@IRSMSX108.ger.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.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [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: Tue, 06 Nov 2018 15:19:12 -0000 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 u= p 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 h= ave been aiming to have sub-trees merged every week, but that's never happe= ned. Jeremy has also made an update to fix the exclusion of the docs direct= ory, 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 tes= t results page. - Agreed that we're all happy to make the relative performance results publ= ic. Jeremy will make this change and notify ci@dpdk.org when this is comple= te. Patchwork Integration: - To make the results more visible, and to ensure that developers and maint= ainers act on them, we agreed that results should be integrated into Patchw= ork, similar to the way that build tests are handled. Jeremy will review th= e 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 measurement= s over time. Abstract for the presentation is: "The DPDK Open Lab is a performance based continuous integration system, su= pported 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 ins= talled, 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 DPD= K on various hardware platforms. This talk will explore how the this system= supports the development community, such as accepting patches based on per= formance and tracking how performance has changed in DPDK over time. We wil= l go over how to navigate and use the Dashboard. We will show how the perfo= rmance has changed in DPDK over the past six months, looking at relative nu= mbers 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 test= s for DPDK, additional capabilities for the dashboard, and making the syste= ms more accessible to the development community."