All performance numbers provided in this document are gathered using following Evaluation Modules unless otherwise specified.
| Name | Description |
|---|---|
| AM62Dx EVM | AM62Dx Evaluation Module rev E1 with ARM running at 1.4GHz, DDR data rate 3733 MT/S |
Table: Evaluation Modules
This document provides performance data for each of the device drivers which are part of the Processor SDK Linux package. This document should be used in conjunction with release notes and user guides provided with the Processor SDK Linux package for information on specific issues present with drivers included in a particular release.
For further information or to report any problems, contact https://e2e.ti.com/ or https://support.ti.com/
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 https://lmbench.sourceforge.net/whatis_lmbench.html and https://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 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.
Execute the LMBench with the following:
cd /opt/ltp ./runltp -P j721e-idk-gw -f ddt/lmbench -s LMBENCH_L_PERF_0001
| Benchmarks | am62dxx_evm-fs: perf |
|---|---|
| af_unix_sock_stream_latency (microsec) | 26.25 (min 23.23, max 29.86) |
| af_unix_socket_stream_bandwidth (mbs) | 1071.71 (min 1058.15, max 1084.28) |
| bw_file_rd-io-1mb (mb/s) | 1348.18 (min 1335.78, max 1359.22) |
| bw_file_rd-o2c-1mb (mb/s) | 696.88 (min 633.61, max 771.01) |
| bw_mem-bcopy-16mb (mb/s) | 1742.80 (min 1730.67, max 1760.18) |
| bw_mem-bcopy-1mb (mb/s) | 1865.40 (min 1833.37, max 1893.94) |
| bw_mem-bcopy-2mb (mb/s) | 1625.86 (min 1561.59, max 1675.32) |
| bw_mem-bcopy-4mb (mb/s) | 1648.95 (min 1618.78, max 1670.84) |
| bw_mem-bcopy-8mb (mb/s) | 1674.23 (min 1590.62, max 1730.10) |
| bw_mem-bzero-16mb (mb/s) | 7939.79 (min 7935.20, max 7947.02) |
| bw_mem-bzero-1mb (mb/s) | 4882.93 (min 1833.37, max 7950.36) |
| bw_mem-bzero-2mb (mb/s) | 4763.62 (min 1561.59, max 7916.52) |
| bw_mem-bzero-4mb (mb/s) | 4781.67 (min 1618.78, max 7926.50) |
| bw_mem-bzero-8mb (mb/s) | 4802.10 (min 1590.62, max 7943.07) |
| bw_mem-cp-16mb (mb/s) | 841.31 (min 833.20, max 851.06) |
| bw_mem-cp-1mb (mb/s) | 4496.61 (min 783.70, max 8222.18) |
| bw_mem-cp-2mb (mb/s) | 4414.12 (min 780.03, max 8041.96) |
| bw_mem-cp-4mb (mb/s) | 4417.08 (min 815.58, max 8002.91) |
| bw_mem-cp-8mb (mb/s) | 4429.55 (min 846.20, max 7980.05) |
| bw_mem-fcp-16mb (mb/s) | 1554.75 (min 1535.21, max 1576.04) |
| bw_mem-fcp-1mb (mb/s) | 4733.08 (min 1539.78, max 7950.36) |
| bw_mem-fcp-2mb (mb/s) | 4701.07 (min 1459.06, max 7916.52) |
| bw_mem-fcp-4mb (mb/s) | 4726.03 (min 1495.51, max 7926.50) |
| bw_mem-fcp-8mb (mb/s) | 4740.18 (min 1540.24, max 7943.07) |
| bw_mem-frd-16mb (mb/s) | 1841.28 (min 1782.13, max 1859.38) |
| bw_mem-frd-1mb (mb/s) | 1754.60 (min 1539.78, max 1975.57) |
| bw_mem-frd-2mb (mb/s) | 1618.86 (min 1459.06, max 1750.09) |
| bw_mem-frd-4mb (mb/s) | 1648.13 (min 1495.51, max 1827.32) |
| bw_mem-frd-8mb (mb/s) | 1658.91 (min 1540.24, max 1849.92) |
| bw_mem-fwr-16mb (mb/s) | 7957.56 (min 7949.65, max 7964.16) |
| bw_mem-fwr-1mb (mb/s) | 5064.88 (min 1899.83, max 8222.18) |
| bw_mem-fwr-2mb (mb/s) | 4873.22 (min 1723.84, max 8041.96) |
| bw_mem-fwr-4mb (mb/s) | 4873.01 (min 1684.21, max 8002.91) |
| bw_mem-fwr-8mb (mb/s) | 4869.76 (min 1689.72, max 7980.05) |
| bw_mem-rd-16mb (mb/s) | 1930.96 (min 1920.08, max 1941.51) |
| bw_mem-rd-1mb (mb/s) | 1704.69 (min 1174.50, max 2232.56) |
| bw_mem-rd-2mb (mb/s) | 1532.41 (min 1099.30, max 1964.96) |
| bw_mem-rd-4mb (mb/s) | 1624.88 (min 1203.55, max 1922.15) |
| bw_mem-rd-8mb (mb/s) | 1714.81 (min 1360.78, max 1945.05) |
| bw_mem-rdwr-16mb (mb/s) | 1609.39 (min 1560.52, max 1682.09) |
| bw_mem-rdwr-1mb (mb/s) | 1008.69 (min 783.70, max 1286.29) |
| bw_mem-rdwr-2mb (mb/s) | 970.31 (min 780.03, max 1168.68) |
| bw_mem-rdwr-4mb (mb/s) | 1109.24 (min 815.58, max 1465.74) |
| bw_mem-rdwr-8mb (mb/s) | 1224.13 (min 846.20, max 1571.40) |
| bw_mem-wr-16mb (mb/s) | 1620.26 (min 1557.03, max 1666.84) |
| bw_mem-wr-1mb (mb/s) | 1214.54 (min 1156.07, max 1286.29) |
| bw_mem-wr-2mb (mb/s) | 1139.75 (min 1096.49, max 1257.66) |
| bw_mem-wr-4mb (mb/s) | 1356.70 (min 1203.55, max 1465.74) |
| bw_mem-wr-8mb (mb/s) | 1534.69 (min 1360.78, max 1571.40) |
| bw_mmap_rd-mo-1mb (mb/s) | 2054.67 (min 2010.97, max 2106.47) |
| bw_mmap_rd-o2c-1mb (mb/s) | 721.65 (min 636.84, max 812.35) |
| bw_pipe (mb/s) | 712.68 (min 661.13, max 740.02) |
| bw_unix (mb/s) | 1071.71 (min 1058.15, max 1084.28) |
| lat_connect (us) | 61.57 (min 50.64, max 72.15) |
| lat_ctx-2-128k (us) | 8.53 (min 7.89, max 9.31) |
| lat_ctx-2-256k (us) | 18.50 (min 6.99, max 40.68) |
| lat_ctx-4-128k (us) | 14.98 (min 8.17, max 29.59) |
| lat_ctx-4-256k (us) | 22.67 (min 7.08, max 97.51) |
| lat_fs-0k (num_files) | 280.00 (min 256.00, max 311.00) |
| lat_fs-10k (num_files) | 123.50 (min 105.00, max 141.00) |
| lat_fs-1k (num_files) | 187.17 (min 173.00, max 203.00) |
| lat_fs-4k (num_files) | 180.67 (min 163.00, max 207.00) |
| lat_mem_rd-stride128-sz1000k (ns) | 30.92 (min 30.56, max 31.60) |
| lat_mem_rd-stride128-sz125k (ns) | 5.57 (min 5.54, max 5.63) |
| lat_mem_rd-stride128-sz250k (ns) | 5.83 (min 5.82, max 5.84) |
| lat_mem_rd-stride128-sz31k (ns) | 3.49 (min 2.15, max 4.20) |
| lat_mem_rd-stride128-sz50 (ns) | 2.15 |
| lat_mem_rd-stride128-sz500k (ns) | 11.53 (min 10.19, max 12.71) |
| lat_mem_rd-stride128-sz62k (ns) | 5.23 (min 5.19, max 5.25) |
| lat_mmap-1m (us) | 53.33 (min 49.00, max 58.00) |
| lat_ops-double-add (ns) | 2.86 (min 2.86, max 2.87) |
| lat_ops-double-div (ns) | 15.74 |
| lat_ops-double-mul (ns) | 2.86 |
| lat_ops-float-add (ns) | 2.86 (min 2.86, max 2.87) |
| lat_ops-float-div (ns) | 9.30 (min 9.30, max 9.31) |
| lat_ops-float-mul (ns) | 2.86 |
| lat_ops-int-add (ns) | 0.72 |
| lat_ops-int-bit (ns) | 0.48 |
| lat_ops-int-div (ns) | 4.30 (min 4.29, max 4.30) |
| lat_ops-int-mod (ns) | 4.53 (min 4.53, max 4.54) |
| lat_ops-int-mul (ns) | 3.09 (min 3.04, max 3.12) |
| lat_ops-int64-add (ns) | 0.72 |
| lat_ops-int64-bit (ns) | 0.48 |
| lat_ops-int64-div (ns) | 6.80 |
| lat_ops-int64-mod (ns) | 5.25 |
| lat_ops-int64-mul (ns) | 3.57 (min 3.54, max 3.64) |
| lat_pagefault (us) | 0.44 |
| lat_pipe (us) | 21.45 (min 20.89, max 21.91) |
| lat_proc-exec (us) | 714.75 (min 702.50, max 721.88) |
| lat_proc-fork (us) | 632.38 (min 613.13, max 654.78) |
| lat_proc-proccall (us) | 0.01 |
| lat_select (us) | 31.59 (min 31.34, max 31.76) |
| lat_sem (us) | 2.73 (min 2.22, max 3.05) |
| lat_sig-catch (us) | 5.60 (min 5.47, max 5.74) |
| lat_sig-install (us) | 0.65 (min 0.58, max 0.71) |
| lat_sig-prot (us) | 0.85 (min 0.71, max 0.92) |
| lat_syscall-fstat (us) | 1.81 (min 1.74, max 1.87) |
| lat_syscall-null (us) | 0.44 (min 0.37, max 0.51) |
| lat_syscall-open (us) | 206.84 (min 162.68, max 241.21) |
| lat_syscall-read (us) | 0.75 (min 0.73, max 0.79) |
| lat_syscall-stat (us) | 4.15 (min 3.99, max 4.26) |
| lat_syscall-write (us) | 0.70 (min 0.66, max 0.75) |
| lat_tcp (us) | 0.89 (min 0.76, max 1.02) |
| lat_unix (us) | 26.25 (min 23.23, max 29.86) |
| latency_for_0.50_mb_block_size (nanosec) | 11.53 (min 10.19, max 12.71) |
| latency_for_1.00_mb_block_size (nanosec) | 15.46 (min 0.00, max 31.60) |
| pipe_bandwidth (mbs) | 712.68 (min 661.13, max 740.02) |
| pipe_latency (microsec) | 21.45 (min 20.89, max 21.91) |
| procedure_call (microsec) | 0.01 |
| select_on_200_tcp_fds (microsec) | 31.59 (min 31.34, max 31.76) |
| semaphore_latency (microsec) | 2.73 (min 2.22, max 3.05) |
| signal_handler_latency (microsec) | 0.65 (min 0.58, max 0.71) |
| signal_handler_overhead (microsec) | 5.60 (min 5.47, max 5.74) |
| tcp_ip_connection_cost_to_localhost (microsec) | 61.57 (min 50.64, max 72.15) |
| tcp_latency_using_localhost (microsec) | 0.89 (min 0.76, max 1.02) |
Dhrystone is a core only benchmark that runs from warm L1 caches in all modern processors. It scales linearly with clock speed.
Please take note, different run may produce different slightly results. This is advised to run this test multiple times in order to get maximum performance numbers.
Execute the benchmark with the following:
runDhrystone
| Benchmarks | am62dxx_evm-fs: perf |
|---|---|
| cpu_clock (mhz) | 1400.00 |
| dhrystone_per_mhz (dmips/mhz) | 2.75 (min 2.60, max 2.90) |
| dhrystone_per_second (dhrystonep) | 6789289.58 (min 6451613.00, max 7142857.00) |
Whetstone is a benchmark primarily measuring floating-point arithmetic performance.
Execute the benchmark with the following:
runWhetstone
| Benchmarks | am62dxx_evm-fs: perf |
|---|---|
| whetstone (mips) | 5833.33 (min 5000.00, max 10000.00) |
Linpack measures peak double precision (64 bit) floating point performance in solving a dense linear system.
| Benchmarks | am62dxx_evm-fs: perf |
|---|---|
| linpack (kflops) | 580360.75 (min 579515.00, max 581724.00) |
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.
Execute the benchmark with the following:
stream_c
| Benchmarks | am62dxx_evm-fs: perf |
|---|---|
| add (mb/s) | 2566.47 (min 2557.40, max 2582.90) |
| copy (mb/s) | 3540.12 (min 3515.30, max 3565.80) |
| scale (mb/s) | 3346.33 (min 3203.90, max 3405.60) |
| triad (mb/s) | 2384.27 (min 2377.90, max 2393.60) |
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.
| Benchmarks | am62dxx_evm-fs: perf |
|---|---|
| cjpeg-rose7-preset (workloads/) | 41.99 (min 41.84, max 42.02) |
| core (workloads/) | 0.30 |
| coremark-pro () | 928.67 (min 892.10, max 957.91) |
| linear_alg-mid-100x100-sp (workloads/) | 14.68 (min 14.68, max 14.69) |
| loops-all-mid-10k-sp (workloads/) | 0.71 |
| nnet_test (workloads/) | 1.08 |
| parser-125k (workloads/) | 8.96 (min 8.77, max 9.26) |
| radix2-big-64k (workloads/) | 63.08 (min 44.67, max 75.93) |
| sha-test (workloads/) | 81.19 (min 80.65, max 81.97) |
| zip-test (workloads/) | 22.66 (min 22.22, max 23.81) |
| Benchmarks | am62dxx_evm-fs: perf |
|---|---|
| cjpeg-rose7-preset (workloads/) | 159.05 (min 158.73, max 161.29) |
| core (workloads/) | 1.20 |
| coremark-pro () | 2592.85 (min 2558.16, max 2639.06) |
| linear_alg-mid-100x100-sp (workloads/) | 56.35 (min 56.24, max 56.43) |
| loops-all-mid-10k-sp (workloads/) | 2.05 (min 2.01, max 2.11) |
| nnet_test (workloads/) | 3.59 |
| parser-125k (workloads/) | 11.93 (min 9.98, max 13.65) |
| radix2-big-64k (workloads/) | 76.45 (min 71.88, max 81.33) |
| sha-test (workloads/) | 266.71 (min 263.16, max 270.27) |
| zip-test (workloads/) | 78.74 (min 74.07, max 83.33) |
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.
| Benchmarks | am62dxx_evm-fs: perf |
|---|---|
| 4m-check (workloads/) | 423.43 (min 421.30, max 428.08) |
| 4m-check-reassembly (workloads/) | 122.51 (min 108.93, max 172.71) |
| 4m-check-reassembly-tcp (workloads/) | 62.57 (min 59.52, max 73.75) |
| 4m-check-reassembly-tcp-cmykw2-rotatew2 (workloads/) | 34.10 (min 33.67, max 34.90) |
| 4m-check-reassembly-tcp-x264w2 (workloads/) | 1.89 (min 1.88, max 1.89) |
| 4m-cmykw2 (workloads/) | 245.65 (min 239.52, max 250.00) |
| 4m-cmykw2-rotatew2 (workloads/) | 47.70 (min 46.77, max 49.75) |
| 4m-reassembly (workloads/) | 91.00 (min 76.45, max 147.06) |
| 4m-rotatew2 (workloads/) | 52.53 (min 51.79, max 54.11) |
| 4m-tcp-mixed (workloads/) | 128.00 (min 126.98, max 129.03) |
| 4m-x264w2 (workloads/) | 1.95 (min 1.93, max 1.98) |
| idct-4m (workloads/) | 19.28 (min 19.16, max 19.76) |
| idct-4mw1 (workloads/) | 19.28 (min 19.15, max 19.74) |
| ippktcheck-4m (workloads/) | 422.45 (min 418.62, max 428.52) |
| ippktcheck-4mw1 (workloads/) | 422.78 (min 419.96, max 426.40) |
| ipres-4m (workloads/) | 101.92 (min 99.60, max 107.84) |
| ipres-4mw1 (workloads/) | 102.01 (min 99.87, max 108.38) |
| md5-4m (workloads/) | 28.00 (min 27.77, max 28.14) |
| md5-4mw1 (workloads/) | 28.03 (min 27.97, max 28.12) |
| rgbcmyk-4m (workloads/) | 63.80 (min 63.41, max 64.54) |
| rgbcmyk-4mw1 (workloads/) | 63.80 (min 63.45, max 64.45) |
| rotate-4ms1 (workloads/) | 23.83 (min 23.29, max 25.80) |
| rotate-4ms1w1 (workloads/) | 23.84 (min 23.28, max 25.80) |
| rotate-4ms64 (workloads/) | 24.14 (min 23.56, max 26.11) |
| rotate-4ms64w1 (workloads/) | 24.14 (min 23.57, max 26.08) |
| x264-4mq (workloads/) | 0.58 |
| x264-4mqw1 (workloads/) | 0.58 |
| Boot Configuration | am62dxx_evm-fs: Boot time in seconds: avg(min,max) |
|---|---|
| Linux boot time from SD with default rootfs (20 boot cycles) | 17.16 (min 16.40, max 18.33) |
Boot time numbers [avg, min, max] are measured from "Starting kernel" to Linux prompt across 20 boot cycles.
Ethernet performance benchmarks were measured using :command:`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, :command:`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 :command:`netperf` test with no bandwidth limit (remove -b/-w options).
In order to start a :command:`netperf` client on one device, the other device must have :command:`netserver` running. To start :command:`netserver`:
netserver [-p <port_number>] [-4 (IPv4 addressing)] [-6 (IPv6 addressing)]Running the following shell script from the DUT will trigger :command:`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 &
doneRunning the following commands will trigger :command:`netperf` clients to measure UDP burst performance for 60 seconds at various burst/datagram sizes and report CPU utilization.
- For UDP egress tests, run :command:`netperf` client from DUT and start :command:`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 :command:`netperf` client from tester and start :command:`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| Frame Size(bytes) | am62dxx_evm-fs: UDP Datagram Size(bytes) (LOCAL_SEND_SIZE) | am62dxx_evm-fs: THROUGHPUT (Mbits/sec) | am62dxx_evm-fs: Packets Per Second (kPPS) | am62dxx_evm-fs: CPU Load % (LOCAL_CPU_UTIL) |
|---|---|---|---|---|
| 64 | 46.03 (min 45.82, max 46.24) | 89.50 (min 89.00, max 90.00) | 38.12 (min 38.01, max 38.23) | |
| 128 | 91.09 (min 90.84, max 91.34) | 89.00 | 38.04 (min 37.99, max 38.09) |
| Frame Size(bytes) | am62dxx_evm-fs: UDP Datagram Size(bytes) (LOCAL_SEND_SIZE) | am62dxx_evm-fs: THROUGHPUT (Mbits/sec) | am62dxx_evm-fs: Packets Per Second (kPPS) | am62dxx_evm-fs: CPU Load % (LOCAL_CPU_UTIL) |
|---|---|---|---|---|
| 64 | 1.97 (min 1.54, max 2.15) | 3.75 (min 3.00, max 4.00) | 2.24 (min 1.52, max 3.73) | |
| 128 | 5.15 (min 5.12, max 5.22) | 5.00 | 2.97 (min 2.13, max 4.33) | |
| 256 | 9.78 (min 9.01, max 10.65) | 4.75 (min 4.00, max 5.00) | 2.84 (min 1.03, max 5.42) | |
| 1024 | 43.09 (min 38.50, max 51.61) | 5.20 (min 5.00, max 6.00) | 3.78 (min 2.73, max 6.02) | |
| 1518 | 60.76 (min 55.35, max 64.77) | 5.20 (min 5.00, max 6.00) | 3.50 (min 2.30, max 5.87) |
| Frame Size(bytes) | am62dxx_evm-fs: UDP Datagram Size(bytes) (LOCAL_SEND_SIZE) | am62dxx_evm-fs: THROUGHPUT (Mbits/sec) | am62dxx_evm-fs: Packets Per Second (kPPS) | am62dxx_evm-fs: CPU Load % (LOCAL_CPU_UTIL) | am62dxx_evm-fs: Packet Loss % |
|---|---|---|---|---|---|
| 64 | 75.95 (min 67.93, max 98.26) | 148.50 (min 133.00, max 192.00) | 36.17 (min 34.38, max 38.15) | 17.56 (min 1.13, max 64.36) | |
| 128 | 134.40 (min 129.62, max 137.51) | 131.33 (min 127.00, max 134.00) | 36.01 (min 33.95, max 38.93) | 2.45 (min 0.78, max 4.73) | |
| 256 | 304.24 (min 272.41, max 387.16) | 148.50 (min 133.00, max 189.00) | 37.26 (min 35.26, max 39.33) | 29.49 (min 0.84, max 62.35) | |
| 1024 | 909.90 (min 871.42, max 937.29) | 111.00 (min 106.00, max 114.00) | 38.69 (min 35.09, max 41.03) | 0.77 (min 0.22, max 1.35) | |
| 1518 | 909.09 (min 860.26, max 930.92) | 77.20 (min 73.00, max 79.00) | 38.12 (min 35.95, max 39.53) | 0.39 (min 0.09, max 1.30) |
| Number of Blocks | am62dxx_evm-fs: Throughput (MB/sec) |
|---|---|
| 150 | 31.76 (min 26.90, max 40.40) |
| Number of Blocks | am62dxx_evm-fs: Throughput (MB/sec) |
|---|---|
| 150 | 27.41 (min 22.40, max 33.30) |
| Algorithm | Buffer Size (in bytes) | am62dxx_evm-fs: throughput (KBytes/Sec) |
|---|---|---|
| aes-128-cbc | 1024 | 24568.83 |
| aes-128-cbc | 16 | 446.98 |
| aes-128-cbc | 16384 | 87168.34 |
| aes-128-cbc | 256 | 7377.41 |
| aes-128-cbc | 64 | 1969.19 |
| aes-128-cbc | 8192 | 73949.18 |
| aes-128-ecb | 1024 | 24998.57 |
| aes-128-ecb | 16 | 453.88 |
| aes-128-ecb | 16384 | 89085.27 |
| aes-128-ecb | 256 | 7518.29 |
| aes-128-ecb | 64 | 2004.20 |
| aes-128-ecb | 8192 | 75653.12 |
| aes-192-cbc | 1024 | 23895.38 |
| aes-192-cbc | 16 | 446.65 |
| aes-192-cbc | 16384 | 78091.61 |
| aes-192-cbc | 256 | 7297.54 |
| aes-192-cbc | 64 | 1949.01 |
| aes-192-cbc | 8192 | 67155.29 |
| aes-192-ecb | 1024 | 24523.09 |
| aes-192-ecb | 16 | 457.21 |
| aes-192-ecb | 16384 | 80439.98 |
| aes-192-ecb | 256 | 7495.51 |
| aes-192-ecb | 64 | 2025.96 |
| aes-192-ecb | 8192 | 69457.24 |
| aes-256-cbc | 1024 | 23421.95 |
| aes-256-cbc | 16 | 447.55 |
| aes-256-cbc | 16384 | 71516.16 |
| aes-256-cbc | 256 | 7258.20 |
| aes-256-cbc | 64 | 1949.67 |
| aes-256-cbc | 8192 | 61909.67 |
| aes-256-ecb | 1024 | 24072.53 |
| aes-256-ecb | 16 | 458.01 |
| aes-256-ecb | 16384 | 73820.84 |
| aes-256-ecb | 256 | 7437.40 |
| aes-256-ecb | 64 | 2014.89 |
| aes-256-ecb | 8192 | 64184.32 |
| sha256 | 1024 | 32333.82 |
| sha256 | 16 | 535.81 |
| sha256 | 16384 | 277938.18 |
| sha256 | 256 | 8409.69 |
| sha256 | 64 | 2122.37 |
| sha256 | 8192 | 183263.23 |
| sha512 | 1024 | 26990.25 |
| sha512 | 16 | 520.24 |
| sha512 | 16384 | 110586.54 |
| sha512 | 256 | 7864.32 |
| sha512 | 64 | 2082.37 |
| sha512 | 8192 | 91439.10 |
| Algorithm | am62dxx_evm-fs: CPU Load |
|---|---|
| aes-128-cbc | 32.00 |
| aes-128-ecb | 34.00 |
| aes-192-cbc | 32.00 |
| aes-192-ecb | 33.00 |
| aes-256-cbc | 32.00 |
| aes-256-ecb | 32.00 |
| sha256 | 95.00 |
| sha512 | 96.00 |
- Listed for each algorithm are the code snippets used to run each
- benchmark test.
time -v openssl speed -elapsed -evp aes-128-cbc