From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: "moving@dpdk.org" <moving@dpdk.org>, "ci@dpdk.org" <ci@dpdk.org>
Subject: [dpdk-ci] DPDK Performance Lab Proposal
Date: Fri, 3 Feb 2017 14:08:56 +0000 [thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA722B6977@IRSMSX108.ger.corp.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
When we started discussing moving DPDK to the Linux Foundation we talked about the possibility of establishing a DPDK lab. We agreed at the time that CI should be done in a distributed way, and Thomas has done great work to put this in place. We also said that it would be good to have a public lab for performance testing, so that we have an open and repeatable way of identifying any performance regressions caused by new contributions to DPDK.
Attached is a first draft of a proposal to define the scope and purpose of a DPDK lab. Once we've agreed on those, we can progress to the next level of detail and determine specific hardware requirements, get a more accurate estimate of hosting costs etc.
Please review and comment on this. For now I think moving@dpdk.org is the most appropriate mailing list for discussion on this because the proposal has been created in response to discussion there and because it's closely linked to discussions on budget etc., but I've copied ci@dpdk.org as well. We can discuss this during next Tuesday's meeting as well and agree on the next steps for progressing this.
Tim
[-- Attachment #2: DPDK Performance Test Lab Proposal - v1.pdf --]
[-- Type: application/pdf, Size: 210615 bytes --]
reply other threads:[~2017-02-03 14:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=26FA93C7ED1EAA44AB77D62FBE1D27BA722B6977@IRSMSX108.ger.corp.intel.com \
--to=tim.odriscoll@intel.com \
--cc=ci@dpdk.org \
--cc=moving@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).