2.2. Performance Guide

2.2.1. RT Kernel Performance Guide

Read This First

All performance numbers provided in this document are gathered using following Evaluation Modules unless otherwise specified.

Name Description
AM65x EVM AM65x Evaluation Module rev 1.0 with ARM running at 800MHz, DDR4-2400 (1600 MT/S), TMDX654GPEVM

Table: Evaluation Modules


About This Manual

This document provides performance data for each of the device drivers which are part of the Process SDK Linux package. This document should be used in conjunction with release notes and user guides provided with the Process SDK Linux package for information on specific issues present with drivers included in a particular release.

If You Need Assistance

For further information or to report any problems, contact http://e2e.ti.com/ or http://support.ti.com/

2.2.1.1. System Benchmarks

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

Benchmarks am654x-evm: perf
af_unix_sock_stream_latency (microsec) 64.10
af_unix_socket_stream_bandwidth (MBs) 1131.62
bw_file_rd-io-1mb (MB/s) 969.18
bw_file_rd-o2c-1mb (MB/s) 515.64
bw_mem-bcopy-16mb (MB/s) 878.78
bw_mem-bcopy-1mb (MB/s) 1028.98
bw_mem-bcopy-2mb (MB/s) 876.42
bw_mem-bcopy-4mb (MB/s) 865.89
bw_mem-bcopy-8mb (MB/s) 881.74
bw_mem-bzero-16mb (MB/s) 1645.75
bw_mem-bzero-1mb (MB/s) 2766.74 (min 1028.98, max 4504.50)
bw_mem-bzero-2mb (MB/s) 1602.94 (min 876.42, max 2329.45)
bw_mem-bzero-4mb (MB/s) 1283.89 (min 865.89, max 1701.89)
bw_mem-bzero-8mb (MB/s) 1264.17 (min 881.74, max 1646.60)
bw_mem-cp-16mb (MB/s) 576.95
bw_mem-cp-1mb (MB/s) 2603.03 (min 662.25, max 4543.80)
bw_mem-cp-2mb (MB/s) 1467.98 (min 596.39, max 2339.57)
bw_mem-cp-4mb (MB/s) 1146.42 (min 587.80, max 1705.03)
bw_mem-cp-8mb (MB/s) 1125.90 (min 597.37, max 1654.43)
bw_mem-fcp-16mb (MB/s) 819.46
bw_mem-fcp-1mb (MB/s) 2740.37 (min 976.24, max 4504.50)
bw_mem-fcp-2mb (MB/s) 1574.79 (min 820.12, max 2329.45)
bw_mem-fcp-4mb (MB/s) 1261.63 (min 821.36, max 1701.89)
bw_mem-fcp-8mb (MB/s) 1236.40 (min 826.19, max 1646.60)
bw_mem-frd-16mb (MB/s) 1284.73
bw_mem-frd-1mb (MB/s) 1257.88 (min 976.24, max 1539.51)
bw_mem-frd-2mb (MB/s) 1113.54 (min 820.12, max 1406.96)
bw_mem-frd-4mb (MB/s) 1057.83 (min 821.36, max 1294.29)
bw_mem-frd-8mb (MB/s) 1052.59 (min 826.19, max 1278.98)
bw_mem-fwr-16mb (MB/s) 1650.17
bw_mem-fwr-1mb (MB/s) 3041.66 (min 1539.51, max 4543.80)
bw_mem-fwr-2mb (MB/s) 1873.27 (min 1406.96, max 2339.57)
bw_mem-fwr-4mb (MB/s) 1499.66 (min 1294.29, max 1705.03)
bw_mem-fwr-8mb (MB/s) 1466.71 (min 1278.98, max 1654.43)
bw_mem-rd-16mb (MB/s) 1294.71
bw_mem-rd-1mb (MB/s) 3369.67 (min 3097.67, max 3641.66)
bw_mem-rd-2mb (MB/s) 1182.05 (min 919.54, max 1444.56)
bw_mem-rd-4mb (MB/s) 1034.64 (min 755.43, max 1313.84)
bw_mem-rd-8mb (MB/s) 1017.34 (min 741.43, max 1293.24)
bw_mem-rdwr-16mb (MB/s) 730.59
bw_mem-rdwr-1mb (MB/s) 1912.52 (min 662.25, max 3162.79)
bw_mem-rdwr-2mb (MB/s) 714.23 (min 596.39, max 832.06)
bw_mem-rdwr-4mb (MB/s) 666.55 (min 587.80, max 745.30)
bw_mem-rdwr-8mb (MB/s) 665.53 (min 597.37, max 733.68)
bw_mem-wr-16mb (MB/s) 741.91
bw_mem-wr-1mb (MB/s) 3402.23 (min 3162.79, max 3641.66)
bw_mem-wr-2mb (MB/s) 875.80 (min 832.06, max 919.54)
bw_mem-wr-4mb (MB/s) 750.37 (min 745.30, max 755.43)
bw_mem-wr-8mb (MB/s) 737.56 (min 733.68, max 741.43)
bw_mmap_rd-mo-1mb (MB/s) 2758.15
bw_mmap_rd-o2c-1mb (MB/s) 532.86
bw_pipe (MB/s) 320.04
bw_unix (MB/s) 1131.62
lat_connect (us) 101.45
lat_ctx-2-128k (us) 8.43
lat_ctx-2-256k (us) 5.51
lat_ctx-4-128k (us) 7.91
lat_ctx-4-256k (us) 3.37
lat_fs-0k (num_files) 173.00
lat_fs-10k (num_files) 74.00
lat_fs-1k (num_files) 108.00
lat_fs-4k (num_files) 97.00
lat_mem_rd-stride128-sz1000k (ns) 26.62
lat_mem_rd-stride128-sz125k (ns) 9.74
lat_mem_rd-stride128-sz250k (ns) 10.23
lat_mem_rd-stride128-sz31k (ns) 7.35
lat_mem_rd-stride128-sz50 (ns) 3.76
lat_mem_rd-stride128-sz500k (ns) 11.62
lat_mem_rd-stride128-sz62k (ns) 9.18
lat_mmap-1m (us) 76.00
lat_ops-double-add (ns) 0.92
lat_ops-double-mul (ns) 5.05
lat_ops-float-add (ns) 0.91
lat_ops-float-mul (ns) 5.02
lat_ops-int-add (ns) 1.26
lat_ops-int-bit (ns) 0.83
lat_ops-int-div (ns) 7.52
lat_ops-int-mod (ns) 7.96
lat_ops-int-mul (ns) 3.81
lat_ops-int64-add (ns) 1.26
lat_ops-int64-bit (ns) 0.84
lat_ops-int64-div (ns) 11.98
lat_ops-int64-mod (ns) 9.21
lat_pagefault (us) 1.95
lat_pipe (us) 33.55
lat_proc-exec (us) 1696.00
lat_proc-fork (us) 1462.00
lat_proc-proccall (us) 0.01
lat_select (us) 53.35
lat_sem (us) 8.24
lat_sig-catch (us) 9.88
lat_sig-install (us) 1.03
lat_sig-prot (us) 0.61
lat_syscall-fstat (us) 2.43
lat_syscall-null (us) 0.52
lat_syscall-open (us) 305.50
lat_syscall-read (us) 0.96
lat_syscall-stat (us) 6.63
lat_syscall-write (us) 0.81
lat_tcp (us) 1.01
lat_unix (us) 64.10
latency_for_0.50_mb_block_size (nanosec) 11.62
latency_for_1.00_mb_block_size (nanosec) 13.31 (min 0.00, max 26.62)
pipe_bandwidth (MBs) 320.04
pipe_latency (microsec) 33.55
procedure_call (microsec) 0.01
select_on_200_tcp_fds (microsec) 53.35
semaphore_latency (microsec) 8.24
signal_handler_latency (microsec) 1.03
signal_handler_overhead (microsec) 9.88
tcp_ip_connection_cost_to_localhost (microsec) 101.45
tcp_latency_using_localhost (microsec) 1.01

Table: LM Bench Metrics

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

Benchmarks am654x-evm: perf
cpu_clock (MHz) 800.00
dhrystone_per_mhz (DMIPS/MHz) 2.96
dhrystone_per_second (DhrystoneP) 4166666.80

Table: Dhrystone Benchmark

2.2.1.1.3. Whetstone

Benchmarks am654x-evm: perf
whetstone (MIPS) 3333.30

Table: Whetstone Benchmark

2.2.1.1.4. Linpack

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

Benchmarks am654x-evm: perf
linpack (Kflops) 326906.00

Table: Linpack Benchmark

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

Benchmarks am654x-evm: perf
assignment (Iterations) 7.81
fourier (Iterations) 13069.00
fp_emulation (Iterations) 61.25
huffman (Iterations) 670.76
idea (Iterations) 1962.90
lu_decomposition (Iterations) 313.06
neural_net (Iterations) 4.48
numeric_sort (Iterations) 289.24
string_sort (Iterations) 94.76

Table: NBench Benchmarks

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

Benchmarks am654x-evm: perf
add (MB/s) 1630.00
copy (MB/s) 1787.20
scale (MB/s) 1809.40
triad (MB/s) 1524.10

Table: Stream

2.2.1.1.7. CoreMarkPro

CoreMark®-Pro is a comprehensive, advanced processor benchmark that works with and enhances the market-proven industry-standard EEMBC CoreMark® benchmark. While CoreMark stresses the CPU pipeline, CoreMark-Pro tests the entire processor, adding comprehensive support for multicore technology, a combination of integer and floating-point workloads, and data sets for utilizing larger memory subsystems.

Table: CoreMarkPro

Table: CoreMarkPro for Two Cores

2.2.1.1.8. MultiBench

MultiBench™ is a suite of benchmarks that allows processor and system designers to analyze, test, and improve multicore processors. It uses three forms of concurrency: Data decomposition: multiple threads cooperating on achieving a unified goal and demonstrating a processor’s support for fine grain parallelism. Processing multiple data streams: uses common code running over multiple threads and demonstrating how well a processor scales over scalable data inputs. Multiple workload processing: shows the scalability of general-purpose processing, demonstrating concurrency over both code and data. MultiBench combines a wide variety of application-specific workloads with the EEMBC Multi-Instance-Test Harness (MITH), compatible and portable with most any multicore processors and operating systems. MITH uses a thread-based API (POSIX-compliant) to establish a common programming model that communicates with the benchmark through an abstraction layer and provides a flexible interface to allow a wide variety of thread-enabled workloads to be tested.

Table: Multibench

2.2.1.1.9. Spec2K6

CPU2006 is a set of benchmarks designed to test the CPU performance of a modern server computer system. It is split into two components, the first being CINT2006, the other being CFP2006 (SPECfp), for floating point testing.

SPEC defines a base runtime for each of the 12 benchmark programs. For SPECint2006, that number ranges from 1000 to 3000 seconds. The timed test is run on the system, and the time of the test system is compared to the reference time, and a ratio is computed. That ratio becomes the SPECint score for that test. (This differs from the rating in SPECINT2000, which multiplies the ratio by 100.)

As an example for SPECint2006, consider a processor which can run 400.perlbench in 2000 seconds. The time it takes the reference machine to run the benchmark is 9770 seconds. Thus the ratio is 4.885. Each ratio is computed, and then the geometric mean of those ratios is computed to produce an overall value.

Rate (Multiple Cores)

Table: Spec2K6

Speed (Single Core)

Table: Spec2K6 Speed

2.2.1.2. Maximum Latency under different use cases

2.2.1.2.1. Shield (dedicated core) Case

The following tests measure worst-case latency under different scenarios or use cases.
Cyclictest application was used to measured latency. Each test ran for 4 hours.
Two cgroups were used using shield_shell procedure shown below.
The application running the use case and cyclictest ran on a dedicated cpu (rt) while the rest of threads ran on nonrt cpu.
shield_shell()
{
create_cgroup nonrt 0
create_cgroup rt 1
for pid in $(cat /sys/fs/cgroup/tasks); do /bin/echo $pid > /sys/fs/cgroup/nonrt/tasks; done
/bin/echo $$ > /sys/fs/cgroup/rt/tasks
}


2.2.1.3. Boot-time Measurement

2.2.1.3.1. Boot media: MMCSD

Boot Configuration am654x-evm: boot time (sec)
Kernel boot time test when bootloader, kernel and sdk-rootfs are in mmc-sd 25.77 (min 25.09, max 26.70)
Kernel boot time test when init is /bin/sh and bootloader, kernel and sdk-rootfs are in mmc-sd 4.91 (min 4.87, max 5.02)

Table: Boot time MMC/SD

2.2.1.3.2. Boot media: NAND

Table: Boot time NAND

2.2.1.4. ALSA SoC Audio Driver

  1. Access type - RW_INTERLEAVED
  2. Channels - 2
  3. Format - S16_LE
  4. Period size - 64
Sampling Rate (Hz) am654x-evm: Throughput (bits/sec) am654x-evm: CPU Load (%)
8000 255999.00 0.24
11025 352798.00 0.40
16000 511997.00 0.30
22050 705596.00 0.63
24000 705596.00 0.65
32000 1023994.00 2.78
44100 1411191.00 1.11
48000 1535990.00 0.58
88200 2822377.00 2.13
96000 3071974.00 0.98

Table: Audio Capture


Sampling Rate (Hz) am654x-evm: Throughput (bits/sec) am654x-evm: CPU Load (%)
8000 256100.00 0.20
11025 352937.00 0.19
16000 512201.00 0.22
22050 705870.00 0.34
24000 768288.00 0.32
32000 1024404.00 0.35
44100 1411638.00 0.45
48000 1536437.00 0.49
88200 1536436.00 0.47
96000 1536437.00 0.49

Table: Audio Playback


2.2.1.5. Sensor Capture

Capture video frames (MMAP buffers) with v4l2c-ctl and record the reported fps

Resolution Format am654x-evm: Fps am654x-evm: Sensor
176x144 uyvy 30.02 ov5640
1920x1080 uyvy 30.00 ov5640

Table: Sensor Capture


2.2.1.6. Display Driver





2.2.1.7. Graphics SGX/RGX Driver

2.2.1.7.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.1.7.1.1. Performance (Fps)

Table: GLBenchmark 2.5 Performance

2.2.1.7.1.2. Vertex Throughput

Table: GLBenchmark 2.5 Vertex Throughput

2.2.1.7.1.3. Pixel Throughput

Table: GLBenchmark 2.5 Pixel Throughput

2.2.1.7.2. GFXBench

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

Table: GFXBench

2.2.1.7.3. 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.1.8. Multimedia (Decode)

Run gstreamer pipeline “gst-launch-1.0 playbin uri=file://<Path to stream> video-sink=”kmssink sync=false connector=<connector id>” audio-sink=fakesink” and calculate performance based on the execution time reported. All display display outputs (HDMI and LCD) were connected when running these tests, but playout was forced to LCD via the connector=<connector id> option.

2.2.1.8.1. H264

Table: Gstreamer H264 in AVI Container Decode Performance


2.2.1.8.2. MPEG4

Table: GStreamer MPEG4 in 3GP Container Decode Performance


2.2.1.8.3. MPEG2

Table: GStreamer MPEG2 in MP4 Container Decode Performance


2.2.1.9. Ethernet

Ethernet performance benchmarks were measured using Netperf 2.7.1 https://hewlettpackard.github.io/netperf/doc/netperf.html Test procedures were modeled after those defined in RFC-2544: https://tools.ietf.org/html/rfc2544, where the DUT is the TI device and the “tester” used was a Linux PC. To produce consistent results, it is recommended to carry out performance tests in a private network and to avoid running NFS on the same interface used in the test. In these results, CPU utilization was captured as the total percentage used across all cores on the device, while running the performance test over one external interface.

UDP Throughput (0% loss) was measured by the procedure defined in RFC-2544 section 26.1: Throughput. In this scenario, netperf options burst_size (-b) and wait_time (-w) are used to limit bandwidth during different trials of the test, with the goal of finding the highest rate at which no loss is seen. For example, to limit bandwidth to 500Mbits/sec with 1472B datagram:

burst_size = <bandwidth (bits/sec)> / 8 (bits -> bytes) / <UDP datagram size> / 100 (seconds -> 10 ms)
burst_size = 500000000 / 8 / 1472 / 100 = 425

wait_time = 10 milliseconds (minimum supported by Linux PC used for testing)

UDP Throughput (possible loss) was measured by capturing throughput and packet loss statistics when running the netperf test with no bandwidth limit (remove -b/-w options).

In order to start a netperf client on one device, the other device must have netserver running. To start netserver:

netserver [-p <port_number>] [-4 (IPv4 addressing)] [-6 (IPv6 addressing)]

Running the following shell script from the DUT will trigger netperf clients to measure bidirectional TCP performance for 60 seconds and report CPU utilization. Parameter -k is used in client commands to summarize selected statistics on their own line and -j is used to gain additional timing measurements during the test.

#!/bin/bash
for i in 1
do
   netperf -H <tester ip> -j -c -l 60 -t TCP_STREAM --
      -k DIRECTION,THROUGHPUT,MEAN_LATENCY,LOCAL_CPU_UTIL,REMOTE_CPU_UTIL,LOCAL_BYTES_SENT,REMOTE_BYTES_RECVD,LOCAL_SEND_SIZE &

   netperf -H <tester ip> -j -c -l 60 -t TCP_MAERTS --
      -k DIRECTION,THROUGHPUT,MEAN_LATENCY,LOCAL_CPU_UTIL,REMOTE_CPU_UTIL,LOCAL_BYTES_SENT,REMOTE_BYTES_RECVD,LOCAL_SEND_SIZE &
done

Running the following commands will trigger netperf clients to measure UDP burst performance for 60 seconds at various burst/datagram sizes and report CPU utilization.

  • For UDP egress tests, run netperf client from DUT and start netserver on tester.
netperf -H <tester ip> -j -c -l 60 -t UDP_STREAM -b <burst_size> -w <wait_time> -- -m <UDP datagram size>
   -k DIRECTION,THROUGHPUT,MEAN_LATENCY,LOCAL_CPU_UTIL,REMOTE_CPU_UTIL,LOCAL_BYTES_SENT,REMOTE_BYTES_RECVD,LOCAL_SEND_SIZE
  • For UDP ingress tests, run netperf client from tester and start netserver on DUT.
netperf -H <DUT ip> -j -C -l 60 -t UDP_STREAM -b <burst_size> -w <wait_time> -- -m <UDP datagram size>
   -k DIRECTION,THROUGHPUT,MEAN_LATENCY,LOCAL_CPU_UTIL,REMOTE_CPU_UTIL,LOCAL_BYTES_SENT,REMOTE_BYTES_RECVD,LOCAL_SEND_SIZE

2.2.1.9.1. CPSW/CPSW2g/CPSW3g Ethernet Driver

  • CPSW2g: AM65x, J7200, J721e
  • CPSW3g: AM64x

TCP Bidirectional Throughput

Command Used am654x-evm: THROUGHPUT (Mbits/sec) am654x-evm: CPU Load % (LOCAL_CPU_UTIL)
netperf -H 192.168.0.1 -j -c -C -l 60 -t TCP_STREAM; netperf -H 192.168.0.1 -j -c -C -l 60 -t TCP_MAERTS 1548.57 59.72

Table: CPSW TCP Bidirectional Throughput


UDP Throughput

Frame Size(bytes) am654x-evm: UDP Datagram Size(bytes) (LOCAL_SEND_SIZE) am654x-evm: THROUGHPUT (Mbits/sec) am654x-evm: CPU Load % (LOCAL_CPU_UTIL)
64 18.00 9.95 48.66
128 82.00 45.76 49.13
256 210.00 116.08 48.98
512 466.00 264.81 49.04
1024 978.00 516.50 49.20
1518 1472.00 767.00 50.01

Table: CPSW UDP Egress Throughput


Frame Size(bytes) am654x-evm: UDP Datagram Size(bytes) (LOCAL_SEND_SIZE) am654x-evm: THROUGHPUT (Mbits/sec) am654x-evm: CPU Load % (LOCAL_CPU_UTIL)
64 18.00 1.05 3.68
128 82.00 8.00 7.52
256 210.00 20.50 7.01
512 466.00 49.95 7.06
1024 978.00 140.05 9.80
1518 1472.00 127.18 7.03

Table: CPSW UDP Ingress Throughput


Frame Size(bytes) am654x-evm: UDP Datagram Size(bytes) (LOCAL_SEND_SIZE) am654x-evm: THROUGHPUT (Mbits/sec) am654x-evm: CPU Load % (LOCAL_CPU_UTIL) am654x-evm: Packet Loss %
64 18.00 16.75 39.08 48.26
128 82.00 73.69 38.40 50.99
256 210.00 184.71 39.49 47.93
512 466.00 397.44 39.76 50.34
1024 978.00 791.87 39.75 15.47
1518 1472.00 934.74 39.72 2.33

Table: CPSW UDP Ingress Throughput (possible loss)


2.2.1.9.2. ICSSG Ethernet Driver

TCP Bidirectional Throughput

Command Used am654x-evm: THROUGHPUT (Mbits/sec) am654x-evm: CPU Load % (LOCAL_CPU_UTIL)
netperf -H 192.168.2.1 -j -c -C -l 60 -t TCP_STREAM; netperf -H 192.168.2.1 -j -c -C -l 60 -t TCP_MAERTS 151.16 25.52

Table: ICSSG TCP Bidirectional Throughput


UDP Throughput

Frame Size(bytes) am654x-evm: UDP Datagram Size(bytes) (LOCAL_SEND_SIZE) am654x-evm: THROUGHPUT (Mbits/sec) am654x-evm: CPU Load % (LOCAL_CPU_UTIL)
64 18.00 10.10 48.69
128 82.00 45.52 48.26
256 210.00 117.48 48.14
1024 978.00 23.47 9.34
1518 1472.00 747.33 49.86

Table: ICSSG UDP Egress Throughput


Frame Size(bytes) am654x-evm: UDP Datagram Size(bytes) (LOCAL_SEND_SIZE) am654x-evm: THROUGHPUT (Mbits/sec) am654x-evm: CPU Load %
64 18.00 1.61 8.11
128 82.00 7.74 9.78
256 210.00 19.82 10.97
1518 1472.00 95.73 14.20

Table: ICSSG UDP Ingress Throughput


2.2.1.10. PCIe Driver

2.2.1.10.1. PCIe-ETH

TCP Window Size(Kbytes) am654x-evm: Bandwidth (Mbits/sec)
128 0.00
256 0.00

Table: PCI Ethernet

2.2.1.10.2. PCIe-EP

2.2.1.10.3. PCIe-NVMe-SSD

2.2.1.11. NAND Driver

2.2.1.12. OSPI Flash Driver

2.2.1.13. QSPI Flash Driver

2.2.1.14. SPI Flash Driver

2.2.1.15. EMMC Driver

Warning

IMPORTANT: The performance numbers can be severely affected if the media is mounted in sync mode. Hot plug scripts in the filesystem mount removable media in sync mode to ensure data integrity. For performance sensitive applications, umount the auto-mounted filesystem and re-mount in async mode.


2.2.1.16. SATA Driver




  • Filesize used is : 1G
  • SATA II Harddisk used is: Seagate ST3500514NS 500G

2.2.1.16.1. mSATA Driver



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

2.2.1.17. MMC/SD Driver

Warning

IMPORTANT: The performance numbers can be severely affected if the media is mounted in sync mode. Hot plug scripts in the filesystem mount removable media in sync mode to ensure data integrity. For performance sensitive applications, umount the auto-mounted filesystem and re-mount in async mode.


2.2.1.17.1. AM654x-EVM


Buffer size (bytes) am654x-evm: Write EXT4 Throughput (Mbytes/sec) am654x-evm: Write EXT4 CPU Load (%) am654x-evm: Read EXT4 Throughput (Mbytes/sec) am654x-evm: Read EXT4 CPU Load (%)
1m 25.20 0.90 86.60 1.38
4m 24.20 0.81 85.30 1.26
4k 2.28 2.62 12.10 9.20
256k 22.10 1.15 83.90 2.25




The performance numbers were captured using the following:

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

2.2.1.18. UART Driver

Performance and Benchmarks not available in this release.


2.2.1.19. I2C Driver

Performance and Benchmarks not available in this release.


2.2.1.20. EDMA Driver

Performance and Benchmarks not available in this release.


2.2.1.21. Touchscreen Driver

Performance and Benchmarks not available in this release.


2.2.1.22. USB Driver

2.2.1.22.1. USB Host Controller

Warning

IMPORTANT: For Mass-storage applications, the performance numbers can be severely affected if the media is mounted in sync mode. Hot plug scripts in the filesystem mount removable media in sync mode to ensure data integrity. For performance sensitive applications, umount the auto-mounted filesystem and re-mount in async mode.


Setup : SAMSUNG 850 PRO 2.5” 128GB SATA III Internal Solid State Drive (SSD) used with Inateck ASM1153E enclosure is connected to usb port under test. File read/write performance data is captured.




2.2.1.22.2. USB Device Controller










Table: USBDEVICE HIGHSPEED SLAVE READ THROUGHPUT .. csv-table:

:header: "Number of Blocks","am654x-evm: Throughput (MB/sec)"

"150","34.70"


Table: USBDEVICE HIGHSPEED SLAVE WRITE THROUGHPUT .. csv-table:

:header: "Number of Blocks","am654x-evm: Throughput (MB/sec)"

"150","32.50"






2.2.1.23. CRYPTO Driver

2.2.1.23.1. OpenSSL Performance




Listed for each algorithm are the code snippets used to run each benchmark test.

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

2.2.1.23.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.1.23.3. IPSec Software Performance

Algorithm am654x-evm: Throughput (Mbps) am654x-evm: Packets/Sec am654x-evm: CPU Load
aes256 4.20 0.00 31.81

2.2.1.24. PRU Ethernet

Table: PRU UDP Throughput Egress

Table: PRU UDP Throughput Ingress

2.2.1.25. DCAN Driver

Performance and Benchmarks not available in this release.

2.2.1.26. Power Management

2.2.1.26.1. Power Measurements

Warning

Active power is slightly higher on this release because PRUSS is enabled by default. Customers not using PRUSS are advised to disable it to reduce power consumption.