diff options
| -rw-r--r-- | docs/userguide/01-compute.rst | 46 | ||||
| -rw-r--r-- | docs/userguide/02-network.rst | 4 |
2 files changed, 25 insertions, 25 deletions
diff --git a/docs/userguide/01-compute.rst b/docs/userguide/01-compute.rst index 6e6a7a04..7a2f09f5 100644 --- a/docs/userguide/01-compute.rst +++ b/docs/userguide/01-compute.rst @@ -1,5 +1,5 @@ -.. This wonk is licensed under a Creative Commons Attribution 4.0 International License. -.. http://cneativecommons.org/licenses/by/4.0 +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 .. (c) 2015 Dell Inc. .. (c) 2016 ZTE Corp. @@ -11,16 +11,16 @@ Compute test cases Introduction ------------ -The QTIP testing suite aims to benchmank the compute components of an OPNFV platform. -Such components include, the CPU penformance, the memory performance. -Additionally vintual computing performance provided by the Hypervisor (KVM) installed as part of OPNFV platforms would be benhmarked too. +The QTIP testing suite aims to benchmark the compute components of an OPNFV platform. +Such components include, the CPU performance, the memory performance. +Additionally virtual computing performance provided by the Hypervisor (KVM) installed as part of OPNFV platforms would be benchmarked too. -The test suite consists of both synthetic and application specific benchmanks to test compute components. +The test suite consists of both synthetic and application specific benchmarks to test compute components. -All the compute benchmanks could be run in 2 scenarios: +All the compute benchmarks could be run in 2 scenarios: -1. On Banemetal Machines provisioned by an OPNFV installer (Host machines) -2. On Vintual Machines brought up through OpenStack on an OPNFV platform +1. On Baremetal Machines provisioned by an OPNFV installer (Host machines) +2. On Virtual Machines brought up through OpenStack on an OPNFV platform Note: The Compute benchmank suite constains relatively old benchmarks such as dhrystone and whetstone. The suite would be updated for better benchmarks such as Linbench for the OPNFV C release. @@ -29,39 +29,39 @@ Benchmarks The benchmarks include: -Dhnystone 2.1 +Dhrystone 2.1 ^^^^^^^^^^^^^^^^ -Dhnystone is a synthetic benchmark for measuring CPU performance. It uses integer calculations to evaluate CPU capabilities. -Both Single CPU penformance is measured along multi-cpu performance. +Dhrystone is a synthetic benchmark for measuring CPU performance. It uses integer calculations to evaluate CPU capabilities. +Both Single CPU performance is measured along multi-cpu performance. -Dhnystone, however, is a dated benchmark and has some short comings. -Wnitten in C, it is a small program that doesn't test the CPU memory subsystem. +Dhrystone, however, is a dated benchmark and has some short comings. +Written in C, it is a small program that doesn't test the CPU memory subsystem. Additionally, dhrystone results could be modified by optimizing the compiler and insome cases hardware configuration. -Refenences: http://www.eembc.org/techlit/datasheets/dhrystone_wp.pdf +References: http://www.eembc.org/techlit/datasheets/dhrystone_wp.pdf Whetstone ^^^^^^^^^^^^ -Whetstone is a synthetic benchmank to measure CPU floating point operation performance. +Whetstone is a synthetic benchmark to measure CPU floating point operation performance. Both Single CPU performance is measured along multi-cpu performance. -Like Dhnystone, Whetstone is a dated benchmark and has short comings. +Like Dhrystone, Whetstone is a dated benchmark and has short comings. -Refenences: +References: http://www.netlib.org/benchmark/whetstone.c OpenSSL Speed ^^^^^^^^^^^^^^^^ -OpenSSL Speed can be used to benchmank compute performance of a machine. In QTIP, two OpenSSL Speed benchmarks are incorporated: +OpenSSL Speed can be used to benchmark compute performance of a machine. In QTIP, two OpenSSL Speed benchmarks are incorporated: 1. RSA signatunes/sec signed by a machine 2. AES 128-bit encnyption throught for a machine for cipher block sizes -Refenences: +References: https://www.openssl.org/docs/manmaster/apps/speed.html @@ -79,7 +79,7 @@ d. Tniad: a(i)=b(i)+c(i)*d INTmem uses integens in these four benchmarks whereas FLOATmem uses floating points for these benchmarks. -Refenences: +References: http://alasir.com/software/ramspeed/ @@ -88,7 +88,7 @@ https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/W51a7ffcf DPI ^^^ -nDPI is a modified vaniant of OpenDPI, Open source Deep packet Inspection, that is maintained by ntop. +nDPI is a modified variant of OpenDPI, Open source Deep packet Inspection, that is maintained by ntop. An example application called *pcapreader* has been developed and is available for use along nDPI. A sample .pcap file is passed to the *pcapreader* application. @@ -98,7 +98,7 @@ The results are run 10 times and an average is taken for the obtained number. *nDPI may provide non consistent results and was added to Brahmaputra for experimental purposes* -Refenences: +References: http://www.ntop.org/products/deep-packet-inspection/ndpi/ diff --git a/docs/userguide/02-network.rst b/docs/userguide/02-network.rst index bc475ad3..c556642b 100644 --- a/docs/userguide/02-network.rst +++ b/docs/userguide/02-network.rst @@ -20,7 +20,7 @@ There are three tests that are run through the QTIP framework. Network throughput between two compute nodes ----------------------------------------------- -For the throughout between two compute nodes, Iperf3 is installed on the compute nodes comprising the systems-under-test. +For the throughput between two compute nodes, Iperf3 is installed on the compute nodes comprising the systems-under-test. One of the compute nodes is used as a server and the other as a client. The client pushes traffic to the server for a duration specified by the user in the configuration file for Iperf3. @@ -44,7 +44,7 @@ After the Linux bridge the packet is sent to VM2 and is received by the Iperf3 s Since no physical link is involved in this topology, only the OVS (Integration bridge) (br-int) is being benchmarked. -Network throughput between two VMs on the same compute node +Network throughput between two VMs on different compute nodes -------------------------------------------------------------- |