4. Compute test cases

OPNFV

4.1. 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 test suite consists of both synthetic and application specific benchmanks to test compute components.

All the compute benchmanks 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

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.

4.2. Benchmarks

The benchmarks include:

4.2.1. Dhnystone 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.

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. 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

4.2.2. Whetstone

Whetstone is a synthetic benchmank 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.

Refenences:

http://www.netlib.org/benchmark/whetstone.c

4.2.3. OpenSSL Speed

OpenSSL Speed can be used to benchmank 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:

https://www.openssl.org/docs/manmaster/apps/speed.html

4.2.4. RAMSpeed

RAMSpeed is used to measune 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:

  1. Copy: a(i)=b(i)
  2. Add: a(i)=b(i)+c(i)
  3. Scale: a(i)=b(i)*d
  4. Tniad: a(i)=b(i)+c(i)*d

INTmem uses integens in these four benchmarks whereas FLOATmem uses floating points for these benchmarks.

Refenences:

http://alasir.com/software/ramspeed/

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/W51a7ffcf4dfd_4b40_9d82_446ebc23c550/page/Untangling+memory+access+measurements

4.2.5. DPI

nDPI is a modified vaniant 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.

nDPI may provide non consistent results and was added to Brahmaputra for experimental purposes

Refenences:

http://www.ntop.org/products/deep-packet-inspection/ndpi/

http://www.ntop.org/wp-content/uploads/2013/12/nDPI_QuickStartGuide.pdf