Rockchip Linux Benchmark KPI
:::info 文档信息
文档标识：RK-CS-YF-375 · 发布版本：V1.1.0 · 发布日期：2021-04-01 · 页数：9 · 语言：英文
原始文档：Rockchip_Introduction_Linux_Benchmark_KPI_EN.pdf
:::
章节大纲
- Rockchip Linux Benchmark KPI（P1）
- Glmark2（P4）
- UnixBench（P4）
- LMbench（P7）
在线预览
若预览无法显示，请直接下载 PDF 后用本地阅读器打开。
1. Glmark2
glmark2 is an OpenGL 2.0 and ES 2.0 benchmark.
The scores of Glmark2's fullscreen and offscreen mode of each chip are shown in the table below:
| Item | RK3399/RK3399Pro | RK3288 | RK3326/PX30 | RK3566/RK3568 |
|---|---|---|---|---|
| Full Screen | 56 | 37 | 30 | 183 |
| Off Screen | 823 | 544 | 301 | 687 |
| GPU Type | Mali-T864 | Mali-T764 | Mali-G31MP2 | Mali-G52 |
The resolution of test screen on different chip platforms is as follows:
| Item | RK3399/RK3399Pro | RK3288 | RK3326/PX30 | RK3568/RK3566 |
|---|---|---|---|---|
| Screen resolution | EDP:1536x2048p60 | EDP:1536x2048p60 | HDMI:1920x1080p60 | MIPI:1920x1080p60 |
The performance of fullscreen mode is related to the screen resolution or ddr type etc. , so the actual performance can refer to the score of off screen mode.
2. UnixBench
The purpose of UnixBench is to provide a basic indicator of the performance of a Unix-like system; hence, multiple tests are used to test various aspects of the system's performance. This is designed to allow you to assess:
the performance of your system when running a single task the performance of your system when running multiple tasks the gain from your system's implementation of parallel processing
UnixBench consists of a number of individual tests that are targeted at specific areas. Here is a summary of what each test does:
Dhrystone
Developed by Reinhold Weicker in 1984. This benchmark is used to measure and compare the performance of computers. The test focuses on string handling, as there are no floating point operations. It is heavily influenced by hardware and software design, compiler and linker options, code optimization, cache memory, wait states, and integer data types.
Whetstone
This test measures the speed and efficiency of floating-point operations. This test contains several modules that are meant to represent a mix of operations typically performed in scientific applications. A wide variety of C functions including sin, cos, sqrt, exp, and log are used as well as integer and floating-point math operations, array accesses, conditional branches, and procedure calls. This test measure both integer and floating-point arithmetic. execl Throughput
This test measures the number of execl calls that can be performed per second. execl is part of the exec family of functions that replaces the current process image with a new process image. It and many other similar commands are front ends for the function execve().
File Copy
This measures the rate at which data can be transferred from one file to another, using various buffer sizes. The file read, write and copy tests capture the number of characters that can be written, read and copied in a specified time (default is 10 seconds).
Pipe Throughput
A pipe is the simplest form of communication between processes. Pipe throughput is the number of times (per second) a process can write 512 bytes to a pipe and read them back. The pipe throughput test has no real counterpart in real-world programming.
Pipe-based Context Switching
This test measures the number of times two processes can exchange an increasing integer through a pipe. The pipe-based context switching test is more like a real-world application. The test program spawns a child process with which it carries on a bi-directional pipe conversation.
Process Creation
This test measure the number of times a process can fork and reap a child that immediately exits. Process creation refers to actually creating process control blocks and memory allocations for new processes, so this applies directly to memory bandwidth. Typically, this benchmark would be used to compare various implementations of operating system process creation calls.
Shell Scripts
The shells scripts test measures the number of times per minute a process can start and reap a set of one, two, four and eight concurrent copies of a shell scripts where the shell script applies a series of transformation to a data file.
System Call Overhead
This estimates the cost of entering and leaving the operating system kernel, i.e., the overhead for performing a system call. It consists of a simple program repeatedly calling the getpid (which returns the process id of the calling process) system call. The time to execute such calls is used to estimate the cost of entering and exiting the kernel.
Graphical Tests
Both 2D and 3D graphical tests are provided; at the moment, the 3D suite in particular is very limited, consisting of the ubgears program. These tests are intended to provide a very rough idea of the system's 2D and 3D graphics performance. Bear in mind, of course, that the reported performance will depend not only on hardware, but on whether your system has appropriate drivers for it.
The reference scores of test items for each chip are as follows:
the performance of your system when running a single task
| Item | RK3399/RK3399Pro | RK3288 | RK3326/PX30 | RK3566 | RK3568 |
|---|---|---|---|---|---|
| Dhrystone 2 using register variables | 19191210.4 | 10626086.6 | 5704897.1 | 12332588.0 | 13176039.3 |
| Double-Precision Whetstone | 3303.5 | 1718.9 | 1565.2 | 2965.9 | 3164.5 |
| Execl Throughput | 2730.8 | 1538.1 | 787.9 | 1483.6 | 1703.0 |
| File Copy 1024 bufsize 2000 maxblocks | 263262.3 | 163001.5 | 125333.2 | 166135.4 | 175490.6 |
| File Copy 256 bufsize 500 maxblocks | 98335.8 | 50635.1 | 37871.9 | 48956.5 | 51574.7 |
| File Copy 4096 bufsize 8000 maxblocks | 677993.2 | 384632.9 | 321189.7 | 440209.9 | 461129.3 |
| Pipe Throughput | 775302.3 | 357578.5 | 300305.5 | 521804.1 | 557997.0 |
| Pipe-based Context Switching | 87345.3 | 54247.5 | 37434.5 | 51766.2 | 53873.8 |
| Process Creation | 4274.2 | 3512.1 | 2086.0 | 3782.4 | 4041.7 |
| Shell Scripts (1 concurrent) | 2944.0 | 2973.3 | 1474.2 | 2352.0 | 2817.2 |
| Shell Scripts (8 concurrent) | 832.4 | 703.2 | 431.7 | 567.3 | 675.6 |
| System Call Overhead | 721899.8 | 624614.1 | 568868.6 | 783414.7 | 836985.7 |
| System Benchmarks Index Score | 654.7 | 421.7 | 290.6 | 456.9 | 497.3 |
the performance of your system when running multiple tasks
| Item | RK3399/RK3399Pro | RK3288 | RK3326/PX30 | RK3566 | RK3568 |
|---|---|---|---|---|---|
| Dhrystone 2 using register variables | 61892645.4 | 41527276.3 | 22821903.2 | 47931915.4 | 51737187.8 |
| Double-Precision Whetstone | 13192.2 | 6870.1 | 6265.7 | 11545.6 | 12431.5 |
| Execl Throughput | 6638.9 | 4127.0 | 2449.4 | 3272.1 | 3951.1 |
| File Copy 1024 bufsize 2000 maxblocks | 253903.6 | 265838.2 | 194293.5 | 236042.5 | 246968.0 |
| File Copy 256 bufsize 500 maxblocks | 74647.0 | 74156.4 | 54107.4 | 65182.9 | 67873.4 |
| File Copy 4096 bufsize 8000 maxblocks | 715699.5 | 709343.4 | 565091.8 | 639035.4 | 700693.2 |
| Pipe Throughput | 3159789.0 | 1323176.0 | 1191104.7 | 2031168.7 | 2191846.5 |
| Pipe-based Context Switching | 298324.6 | 134686.9 | 154652.2 | 202912.5 | 212649.7 |
| Process Creation | 11834.7 | 7412.8 | 5183.1 | 7036.5 | 7932.7 |
| Shell Scripts (1 concurrent) | 7420.0 | 5710.9 | 3587.9 | 4613.8 | 5473.0 |
| Shell Scripts (8 concurrent) | 952.5 | 744.6 | 477.4 | 593.1 | 707.7 |
| System Call Overhead | 2514699.7 | 2392234.7 | 2206337.3 | 2815382.8 | 3028273.6 |
| System Benchmarks Index Score | 1402.8 | 989.5 | 746.4 | 1039.1 | 1146.5 |
3. LMbench
lmbench is a suite of simple, portable, ANSI/C microbenchmarks for UNIX/POSIX. In general, it measures two key features: latency and bandwidth.
Things need to focus on LMbench include the following:
Latency benchmarks
Context switching Networking: connection establishment, pipe, TCP, UDP, and RPC hot potato File system creates and deletes Process Creation Signal handling System call overhead Memory read latency Bandwidth benchmarks. Cached file read Memory copy (bcopy) Memory read Memory write Pipe TCP Miscellanious
Processor clock rate calculation the performance of your system when running latency benchmarks. (microseconds)
| Item | RK3399/RK3399Pro | RK3288 | RK3326/PX30 | RK3566 | RK3568 |
|---|---|---|---|---|---|
| Simple syscall | 0.2228 | 0.2126 | 0.2176 | 0.1798 | 0.1681 |
| Simple read | 0.3385 | 0.5989 | 0.6965 | 0.4748 | 0.4453 |
| Simple write | 0.2828 | 0.3777 | 0.5637 | 0.3397 | 0.3255 |
| Simple stat | 1.3041 | 2.9836 | 4.1538 | 2.2721 | 2.1151 |
| Simple fstat | 0.3456 | 0.6527 | 0.6581 | 0.5040 | 0.4721 |
| Simple open/close | 3.0633 | 5.2514 | 7.7892 | 6.3818 | 5.7568 |
| Signal handler installation | 0.4103 | 0.6593 | 0.6882 | 0.4384 | 0.4116 |
| Signal handler overhead | 1.9096 | 4.3894 | 4.5098 | 4.1982 | 3.9874 |
| Pipe latency | 14.3626 | 23.8091 | 36.1158 | 28.3653 | 26.4768 |
| AF UNIX sock _ stream latency | 19.0106 | 21.9593 | 50.0182 | 48.2105 | 36.8146 |
| Process fork+exit | 254.8182 | 390.5714 | 668.1250 | 693.1111 | 632.1250 |
| Process fork+execve | 281.0526 | 417.2308 | 754.7143 | 752.3750 | 448.5833 |
| UDP latency | 28.8465 | 53.3952 | 64.4354 | 45.6886 | 68.6856 |
| TCP latency | 36.1384 | 65.4973 | 77.5462 | 57.7789 | 88.9926 |
| STREAM2 sum latency (nanoseconds) | 1.89 | 3.35 | 5.96 | 2.41 | 2.23 |
the performance of your system when running bandwidth benchmarks. (MB/sec)
| Item | RK3399/RK3399Pro | RK3288 | RK3326/PX30 | RK3566 | RK3568 |
|---|---|---|---|---|---|
| AF UNIX sock _ stream bandwidth | 3751.28 | 2545.44 | 1181.90 | 2178.34 | 1759.47 |
| Pipe bandwidth | 1390.20 | 804.06 | 805.99 | 894.72 | 1041.33 |
| STREAM2 sum bandwidth | 4237.37 | 2385.57 | 1342.32 | 3320.23 | 3595.10 |