diff options
| author |   Billy O'Mahony <billy.o.mahony@intel.com> | 2015-08-05 17:40:42 +0100 |
|---|---|---|
| committer |   Maryam Tahhan <maryam.tahhan@intel.com> | 2015-08-12 10:58:14 +0000 |
| commit | 47b004f7cc627a16afc8462480065479d0eafaae (patch) | |
| tree | 7ade60cf1fc859519cc3caf6c916efa47622f2b0 | |
| parent | 0eff3e49f89c98f7332cae91cdac296ac5e0ac4b (diff) | |
test_spec: Clarify LTD.CPU.RFC2544.0PacketLoss
Make changes based on comments from review at VSPERF weekly call 2015-08-05.
JIRA: VSPERF-2
Change-Id: I141c2b35c5469270ba8e3ecfdf88b93ec8e3d35a
Signed-off-by: Billy O'Mahony<billy.o.mahony@intel.com>
Reviewed-by: Al Morton <acmorton@att.com>
Reviewed-by: Eugene Snider <Eugene.Snider@huawei.com>
Reviewed-by: Maryam Tahhan <maryam.tahhan@intel.com>
Reviewed-by: Gurpreet Singh <gurpreet.singh@spirent.com>
Reviewed-by: Tv Rao <tv.rao@freescale.com>
| -rwxr-xr-x | test_spec/vswitchperf_ltd.md | 36 |
1 files changed, 36 insertions, 0 deletions
diff --git a/test_spec/vswitchperf_ltd.md b/test_spec/vswitchperf_ltd.md index 4aec9b80..51a493b0 100755 --- a/test_spec/vswitchperf_ltd.md +++ b/test_spec/vswitchperf_ltd.md @@ -1305,6 +1305,42 @@ The starting point for defining the suite of tests for benchmarking the performa <br/> +<a name="CPUTests"></a> +####2.3.4 CPU and memory consumption + + The following tests will profile a virtual switch's CPU and memory + utilization under various loads and circumstances. + + The following list is not exhaustive but should indicate the type of tests + that should be required. It is expected that more will be added. + +<br/> + - #####Test ID: LTD.CPU.RFC2544.0PacketLoss + **Title**: RFC 2544 0% Loss Compute Test + + **Prerequisite Test**: + + **Priority**: + + **Description**: + + The aim of this test is to understand the overall performance of the system when a CPU intensive application is run on the same DUT as the Virtual Switch. For each frame size, an LTD.Throughput.RFC2544.PacketLossRatio (0% Packet Loss) test should be performed. Throughout the entire test a CPU intensive application should be run on all cores on the system not in use by the Virtual Switch. For NUMA system only cores on the same NUMA node are loaded. + + It is recommended that stress-ng be used for loading the non-Virtual Switch cores but any stress tool MAY be used. + + **Expected Result**: + + **Metrics Collected**: + + The following are the metrics collected for this test: + + - CPU utilization of the cores running the Virtual Switch. + - The number of identity of the cores allocated to the Virtual Switch. + - The configuration of the stress tool (for example the command line parameters used to start it.) + +---- + + <a name="SummaryList"></a> ####2.3.9 Summary List of Tests - LTD.Throughput.RFC2544.PacketLossRatio |