From: Lijuan Tu <lijuan.tu@intel.com>
To: dts@dpdk.org
Cc: Lijuan Tu <lijuan.tu@intel.com>
Subject: [dts] [next][PATCH V1 2/2] conf/nic_single_core_perf: clarify the value of tolerence
Date: Sat, 8 Sep 2018 09:17:02 +0800 [thread overview]
Message-ID: <1536369422-184743-3-git-send-email-lijuan.tu@intel.com> (raw)
In-Reply-To: <1536369422-184743-1-git-send-email-lijuan.tu@intel.com>
Signed-off-by: Lijuan Tu <lijuan.tu@intel.com>
---
conf/nic_single_core_perf.cfg | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/conf/nic_single_core_perf.cfg b/conf/nic_single_core_perf.cfg
index da1a050..be4f130 100644
--- a/conf/nic_single_core_perf.cfg
+++ b/conf/nic_single_core_perf.cfg
@@ -6,7 +6,7 @@
# - test_duration is how many seconds each combination performance will
# be recorded.
# - accepted_tolerance defines the accepted tolerance between test
-# results and expected numbers.
+# results and expected numbers, value "2" means "2%"
# - expected_throughput is a dictionary defining expected throughput
# numbers based on NIC, and the pattern is
# {'NIC': {'frame size': {'descriptor number': 'excepted throughput'}}}
@@ -22,7 +22,7 @@
update_expected = True
test_parameters = {64: [512, 2048]}
test_duration = 60
-accepted_tolerance = 1
+accepted_tolerance = 2
expected_throughput = {'fortville_spirit': {64: {512: 62.35, 2048: 47.89}},
'niantic': {64: {128: 53.435, 512: 53.699, 2048: 42.798}},
'fortville_25g': {64: {512: 62.35, 2048: 47.651}},
--
1.8.3.1
prev parent reply other threads:[~2018-09-07 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-08 1:17 [dts] [next][PATCH V1 0/2]redefine tolerance for single core performance testing Lijuan Tu
2018-09-08 1:17 ` [dts] [next][PATCH V1 1/2] tests/nic_single_core_perf: redefine accecpt_tolerance Lijuan Tu
2018-09-08 1:17 ` Lijuan Tu [this message]
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=1536369422-184743-3-git-send-email-lijuan.tu@intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@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).