DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick MacArthur <pmacarth@iol.unh.edu>
To: ci@dpdk.org
Cc: dpdklab@iol.unh.edu
Subject: [dpdk-ci] RFC: dashboard mockup
Date: Thu, 10 May 2018 11:51:06 -0400	[thread overview]
Message-ID: <CABj6NQxZ=TXo0rQT8B=CbSJ7bCA43ZDy_apnPQzs+wxF=hLLOg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]

Hi, all,

There was some brief discussion on the last call about the dashboard
for reporting results from the performance regression testing.

I have attached an initial mockup of what I currently plan to
implement, mostly to start a discussion.

Basically what I am envisioning is to essentially have two dashboards.
The first dashboard would show each pending patchset and its status in
the regression testing system, so that we can easily spot which
patchsets need attention, whether it be manually preparing a tarball
to build, missing dependencies on the test systems, or the testing
showed a possible performance regression. The second would be private
to each vendor and show trends in the performance changes of the DPDK
master (and possibly next-net) and the incoming patchsets, which would
help vendors to tune the expected performance numbers on their
hardware accordingly.

Please let me know if you have any questions or feedback on this
mockup, or if there is anything that you think is missing.

Thanks,
Patrick

-- 
Patrick MacArthur
Research and Development, High Performance Networking and Storage
UNH InterOperability Laboratory

[-- Attachment #2: dashboard_mockup_1.pdf --]
[-- Type: application/pdf, Size: 41107 bytes --]

                 reply	other threads:[~2018-05-10 15:51 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='CABj6NQxZ=TXo0rQT8B=CbSJ7bCA43ZDy_apnPQzs+wxF=hLLOg@mail.gmail.com' \
    --to=pmacarth@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    /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).