From 1c5f0ba83b4cccf98df24d939768a74294cc7498 Mon Sep 17 00:00:00 2001 From: Nauman_Ahad Date: Wed, 20 Jan 2016 14:08:27 +0500 Subject: Documents for QTIP Compute and Storage Testcases Documents list storage and compute benchmarks and testcases included in B release for QTIP. Documents in .rst format Change-Id: Ifb6d09552ba4ff9272110062cda9e66fb6c32fe6 Signed-off-by: Nauman_Ahad --- docs/compute_testcases.rst | 71 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 71 insertions(+) create mode 100644 docs/compute_testcases.rst (limited to 'docs/compute_testcases.rst') diff --git a/docs/compute_testcases.rst b/docs/compute_testcases.rst new file mode 100644 index 00000000..4463691b --- /dev/null +++ b/docs/compute_testcases.rst @@ -0,0 +1,71 @@ +Qtip Compute testcases +====================== +============ +Introduction +============ + +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 benhmarked too. + +The test suite consists of both synthetic and application specific benchmarks to test compute components. + +All the compute benchmarks could be run in 2 scenarios: + +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 benchmark 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. + +============ +Benchmarks +============ + + +The benchmarks include: + +1. Dhrystone 2.1 + +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. + + +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. + +References: + +2. Whetstone + +Whetstone is a synthetic benchmark to measure CPU floating point operation performance. Both Single CPU performance is measured along multi-cpu performance. + +Like Dhrystone, Whetstone is a dated benchmark and has short comings. + +References: + +3. OpenSSL Speed + +OpenSSL Speed can be used to benchmark compute performance of a machine. In QTIP, two OpenSSL Speed benchmarks are incorporated: +1. RSA signatures/sec signed by a machine +2. AES 128-bit encryption throught for a machine for cipher block sizes + +References + +4. RAMSpeed + +RAMSpeed is used to measure a machine's memory perfomace. The problem(array)size is large enough to ensure Cache Misses so that the main machine memory is used. INTmem and FLOATmem benchmarks are executed in 4 different scenarios: + +a. Copy: a(i)=b(i) +b. Add: a(i)=b(i)+c(i) +c. Scale: a(i)=b(i)*d +d. Triad: a(i)=b(i)+c(i)*d + +INTmem uses integers in these four benchmarks whereas FLOATmem uses floating points for these benchmarks. + + +5. DPI + +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. nDPI classifies traffic in the pcap file into different categories based on string matching . The *pcapreader* application provides a throughput number for the rate at which traffic was classified, indicating a machine's computational performance. The results are run 10 times and an average is taken for the obtained number. -- cgit 1.2.3-korg