diff options
| author |   Peter Mikus <pmikus@cisco.com> | 2017-05-22 09:35:17 +0200 |
|---|---|---|
| committer | Peter Mikus <pmikus@cisco.com> | 2017-05-25 05:39:30 +0000 |
| commit | 10649b3ce07bbb3144d196c403d8c1fa65ddf116 (patch) | |
| tree | e76a123f6c4fe1390aab02fbbc67a28ac2e714c2 /docs/report/vpp_performance_tests/overview.rst | |
| parent | e6e0c3ad0236d3b2ffb91ae757d84acfb97273b5 (diff) | |
CSIT-612 Report: Minimization of hand-crafted content.
- replace dynamic text content and links by variables.
Change-Id: I1a7ec371fc80af3c9dd416bf91dd2c639097cf1e
Signed-off-by: Peter Mikus <pmikus@cisco.com>
Diffstat (limited to 'docs/report/vpp_performance_tests/overview.rst')
| -rw-r--r-- | docs/report/vpp_performance_tests/overview.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/report/vpp_performance_tests/overview.rst b/docs/report/vpp_performance_tests/overview.rst index 3ee9b2b955..ccf8063ec2 100644 --- a/docs/report/vpp_performance_tests/overview.rst +++ b/docs/report/vpp_performance_tests/overview.rst @@ -194,7 +194,7 @@ Performance Tests Naming ------------------------ CSIT |release| follows a common structured naming convention for all -performance and system functional tests, introduced in CSIT rls1701. +performance and system functional tests, introduced in CSIT |release-1|. The naming should be intuitive for majority of the tests. Complete description of CSIT test naming convention is provided on `CSIT test naming wiki @@ -313,8 +313,8 @@ Methodology: KVM VM vhost ------------------------- CSIT |release| introduced environment configuration changes to KVM Qemu vhost- -user tests in order to more representatively measure VPP-17.04 performance in -configurations with vhost-user interfaces and VMs. +user tests in order to more representatively measure |vpp-release| performance +in configurations with vhost-user interfaces and VMs. Current setup of CSIT FD.io performance lab is using tuned settings for more optimal performance of KVM Qemu: @@ -357,7 +357,7 @@ specific configuration. TRex is installed and run on the TG compute node. The typical procedure is: - If the TRex is not already installed on TG, it is installed in the - suite setup phase - see `TRex intallation <https://gerrit.fd.io/r/gitweb?p=csit.git;a=blob;f=resources/tools/t-rex/t-rex-installer.sh;h=8090b7568327ac5f869e82664bc51b24f89f603f;hb=refs/heads/rls1704>`_. + suite setup phase - see `TRex intallation`_. - TRex configuration is set in its configuration file :: @@ -366,7 +366,7 @@ TRex is installed and run on the TG compute node. The typical procedure is: - TRex is started in the background mode :: - sh -c 'cd /opt/trex-core-2.22/scripts/ && sudo nohup ./t-rex-64 -i -c 7 --iom 0 > /dev/null 2>&1 &' > /dev/null + sh -c 'cd /opt/trex-core-2.25/scripts/ && sudo nohup ./t-rex-64 -i -c 7 --iom 0 > /dev/null 2>&1 &' > /dev/null - There are traffic streams dynamically prepared for each test. The traffic is sent and the statistics obtained using trex_stl_lib.api.STLClient. |