2.2. Linux Performance Guide¶

2.2.1.1. LMBench¶

LMBench is a collection of microbenchmarks of which the memory bandwidth and latency related ones are typically used to estimate processor memory system performance. More information about lmbench at http://lmbench.sourceforge.net/whatis_lmbench.html and http://lmbench.sourceforge.net/man/lmbench.8.html

Latency: lat_mem_rd-stride128-szN, where N is equal to or smaller than the cache size at given level measures the cache miss penalty. N that is at least double the size of last level cache is the latency to external memory.

Bandwidth: bw_mem_bcopy-N, where N is is equal to or smaller than the cache size at a given level measures the achievable memory bandwidth from software doing a memcpy() type operation. Typical use is for external memory bandwidth calculation. The bandwidth is calculated as byte read and written counts as 1 which should be roughly half of STREAM copy result.

Table: LM Bench Metrics

2.2.1.2. Dhrystone¶

Dhrystone is a core only benchmark that runs from warm L1 caches in all modern processors. It scales linearly with clock speed. For standard ARM cores the DMIPS/MHz score will be identical with the same compiler and flags.

Table: Dhrystone Benchmark

2.2.1.3. Whetstone¶

Table: Whetstone Benchmark

2.2.1.4. Linpack¶

Linpack measures peak double precision (64 bit) floating point performance in solving a dense linear system.

Table: Linpack Benchmark

2.2.1.5. NBench¶

NBench which stands for Native Benchmark is used to measure macro benchmarks for commonly used operations such as sorting and analysis algorithms. More information about NBench at https://en.wikipedia.org/wiki/NBench and https://nbench.io/articles/index.html

Table: NBench Benchmarks

2.2.1.6. Stream¶

STREAM is a microbenchmark for measuring data memory system performance without any data reuse. It is designed to miss on caches and exercise data prefetcher and speculative accesses. It uses double precision floating point (64bit) but in most modern processors the memory access will be the bottleneck. The four individual scores are copy, scale as in multiply by constant, add two numbers, and triad for multiply accumulate. For bandwidth, a byte read counts as one and a byte written counts as one, resulting in a score that is double the bandwidth LMBench will show.

Table: Stream

2.2.2.1. Boot media: MMCSD¶

Table: Boot time MMC/SD

2.2.5.1. GLBenchmark¶

Run GLBenchmark and capture performance reported Display rate (Fps), Fill rate, Vertex Throughput, etc. All display outputs (HDMI, Displayport and/or LCD) are connected when running these tests

2.2.5.2. Glmark2¶

Run Glmark2 and capture performance reported (Score). All display outputs (HDMI, Displayport and/or LCD) are connected when running these tests

Table: Glmark2

2.2.6.1. mSATA Driver¶

AM57XX-EVM

• Filesize used is : 1G
• MSATA Harddisk used is: SMS200S3/30G Kingston mSATA SSD drive

2.2.7.1. AM57XX-EVM¶

The performance numbers were captured using the following:

• SanDisk 8GB MicroSDHC Class 10 Memory Card
• Partition was mounted with async option

2.2.8.1. AM57XX-EVM¶

The performance numbers were captured using the following:

• SanDisk 8GB MicroSDHC Class 10 Memory Card

2.2.9.1. USB Device Controller¶

Table: USBDEVICE HIGHSPEED SLAVE READ THROUGHPUT

Table: USBDEVICE HIGHSPEED SLAVE WRITE THROUGHPUT

2.2.10.1. OpenSSL Performance¶

::

time -v openssl speed -elapsed -evp aes-128-cbc

2.2.10.2. IPSec Hardware Performance¶

Note: queue_len is set to 300 and software fallback threshold set to 9 to enable software support for optimal performance

2.2.10.3. IPSec Software Performance¶