From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Wan, Zhe" <zhe.wan@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Wan, Zhe" <zhe.wan@intel.com>
Subject: Re: [dts] [PATCH V1] test_plans/efd: test plan revise
Date: Sun, 24 Mar 2019 19:14:04 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA45D1D@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1552914854-24357-1-git-send-email-zhe.wan@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Zhe
> Sent: Monday, March 18, 2019 6:14 AM
> To: dts@dpdk.org
> Cc: Wan, Zhe <zhe.wan@intel.com>
> Subject: [dts] [PATCH V1] test_plans/efd: test plan revise
>
> From: Zhe Wan <zhe.wan@intel.com>
>
> Signed-off-by: Zhe Wan <zhe.wan@intel.com>
> ---
> test_plans/efd_test_plan.rst | 43 +++++++++++++++++++++++++++++-------------
> -
> 1 file changed, 29 insertions(+), 14 deletions(-)
>
> diff --git a/test_plans/efd_test_plan.rst b/test_plans/efd_test_plan.rst index
> d6962e7..dfde28a 100644
> --- a/test_plans/efd_test_plan.rst
> +++ b/test_plans/efd_test_plan.rst
> @@ -58,6 +58,9 @@ Two ports connect to packet generator.
>
> DUT board must be two sockets system and each cpu have more than 16 lcores.
>
> +Unit test cases
> +===================
> +
> Test Case: EFD function unit test
> ---------------------------------
> Start test application and run efd unit test::
> @@ -77,28 +80,20 @@ Verify when key size increased, no significant increment
> in cpu cycles.
> Verify when value bits increased, no significant increment in cpu cycles.
> Compare with cuckoo hash performance result, lookup cycles should be less.
>
> -Test Case: Load balancer performance based on EFD
> --------------------------------------------------
> +Performance test cases
> +==============================
> In EFD sample, EFD work as a flow-level load balancer. Flows are received at a
> front end server before being forwarded to the target back end server for
> processing. This case will measure the performance of flow distribution with
> different parameters.
>
> -Value bits: number of bits of value that be stored in EFD table
> Nodes: number of back end nodes
> Entries: number of flows to be added in EFD table
> +Value bits: number of bits of value that be stored in EFD table
>
> -+--------------+-------+-----------+------------+
> -| Value Bits | Nodes | Entries | Throughput |
> -+--------------+-------+-----------+------------+
> -| 8 | 2 | 2M | |
> -+--------------+-------+-----------+------------+
> -| 16 | 2 | 2M | |
> -+--------------+-------+-----------+------------+
> -| 24 | 2 | 2M | |
> -+--------------+-------+-----------+------------+
> -| 32 | 2 | 2M | |
> -+--------------+-------+-----------+------------+
> +Test Case: Load balancer performance based on node numbers
> +----------------------------------------------------------------------
> +This case will measure the performance based on node numbers.
>
> +--------------+-------+-----------+------------+
> | Value Bits | Nodes | Entries | Throughput |
> @@ -120,6 +115,10 @@ Entries: number of flows to be added in EFD table
> | 8 | 8 | 2M | |
> +--------------+-------+-----------+------------+
>
> +Test Case: Load balancer performance based on flow numbers
> +-----------------------------------------------------------------------
> +This case will measure the performance based on flow numbers.
> +
> +--------------+-------+-----------+------------+
> | Value Bits | Nodes | Entries | Throughput |
> +--------------+-------+-----------+------------+
> @@ -135,3 +134,19 @@ Entries: number of flows to be added in EFD table +----
> ----------+-------+-----------+------------+
> | 8 | 2 | 32M | |
> +--------------+-------+-----------+------------+
> +
> +Test Case: Load balancer performance based on value bits
> +-----------------------------------------------------------------------
> +This case will measure the performance based on value bits.
> +
> ++--------------+-------+-----------+------------+
> +| Value Bits | Nodes | Entries | Throughput |
> ++--------------+-------+-----------+------------+
> +| 8 | 2 | 2M | |
> ++--------------+-------+-----------+------------+
> +| 16 | 2 | 2M | |
> ++--------------+-------+-----------+------------+
> +| 24 | 2 | 2M | |
> ++--------------+-------+-----------+------------+
> +| 32 | 2 | 2M | |
> ++--------------+-------+-----------+------------+
> --
> 1.8.3.1
prev parent reply other threads:[~2019-03-24 19:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 13:14 Zhe
2019-03-24 19:14 ` Tu, Lijuan [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=8CE3E05A3F976642AAB0F4675D0AD20E0BA45D1D@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=zhe.wan@intel.com \
/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).