From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: "ci@dpdk.org" <ci@dpdk.org>
Subject: [dpdk-ci] Minutes of DPDK Lab Meeting, November 20th
Date: Wed, 21 Nov 2018 10:48:31 +0000 [thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAB77BF012@IRSMSX108.ger.corp.intel.com> (raw)
Relative performance results are now public. Jeremy's blog has also been published (https://www.dpdk.org/blog/2018/11/19/dpdk-community-lab-publishes-relative-performance-testing-results/).
Test results are now integrated into Patchwork.
An initial set of graphs is available at: https://lab.dpdk.org/results/dashboard/stats/. These generated a lot of discussion. Agreed the following:
- The Cumulative graphs didn't show any useful data and have been removed.
- Jeremy has documented the exact data that's being shown: https://mails.dpdk.org/archives/ci/2018-November/000289.html
- Intel 10Gbps results are not stable. Lijuan will work with Jeremy to investigate this.
- Discussed possibility of adding graph showing trend in master performance over time (per release and/or else daily/weekly). UNH will investigate, but currently the database doesn't store performance results for previous releases.
Luca asked about testing of LTS/stable releases:
- Highest priority is LTS releases. We can look at stable releases later.
- Jeremy will add this to the backlog.
Discussed whether the UNH task backlog could be made accessible. Jeremy will investigate. If this isn't possible, then he can send a periodic snapshot.
next reply other threads:[~2018-11-21 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 10:48 O'Driscoll, Tim [this message]
2018-11-21 11:11 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=26FA93C7ED1EAA44AB77D62FBE1D27BAB77BF012@IRSMSX108.ger.corp.intel.com \
--to=tim.odriscoll@intel.com \
--cc=ci@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).