From: Owen Hilyard <ohilyard@iol.unh.edu>
To: ci@dpdk.org
Cc: dpdklab <dpdklab@iol.unh.edu>, Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-ci] DTS Performance Improvements
Date: Thu, 3 Jun 2021 10:28:29 -0400 [thread overview]
Message-ID: <CAHx6DYBwgoNT5AXBt3hahEtUD6yvk-3k_dgoi7e6H_b35_XReg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
Hello Everyone,
I've added another section to the DTS Usability and Developer Feedback
Document
<https://docs.google.com/document/d/1c5S0_mZzFvzZfYkqyORLT2-qNvUb-fBdjA6DGusy4yM/edit#heading=h.bli76tj5btqm>
(Performance
Improvements) which contains my suspicions about the slow parts of DTS. I
would like to reiterate that this is just my experience from watching DTS
run many times, and is not backed up by data. The only piece of information
that I have that is not in there, because it is CI specific, is that having
multiple NICs in a server is essentially a multiplier on the amount of time
it takes to deliver complete feedback. When I tested nine months ago, I
found that it takes well over 24 hours to run all of DTS, so a system with
2 NICs would take more than 2 days, 3 NICs would take more than 3, etc.
Owen Hilyard.
[-- Attachment #2: Type: text/html, Size: 923 bytes --]
reply other threads:[~2021-06-03 14:29 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=CAHx6DYBwgoNT5AXBt3hahEtUD6yvk-3k_dgoi7e6H_b35_XReg@mail.gmail.com \
--to=ohilyard@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--cc=thomas@monjalon.net \
/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).