Open geerlingguy opened 1 year ago
github-actions[bot]
commented
1 year ago This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark issues as stale.
aspencuozzo
commented
5 months ago Would be very interested to see some of these numbers if anyone could run tests, particularly curious how power draw compares to the standard Pi 4 as the CM4 datasheet says it uses slightly less.
geerlingguy
commented
5 months ago @aspencuozzo - Ha! I completely forgot I haven't filled in all the details here. Will do so today.
Basic information
Linux/system information
Benchmark results
CPU
Power
stress-ng --matrix 0): 4.6 Wtop500HPL benchmark: 5.2 WDisk
Samsung 512GB Pro Plus microSD card
Network
iperf3results:iperf3 -c $SERVER_IP: 938 Mbpsiperf3 -c $SERVER_IP --reverse: 942 Mbpsiperf3 -c $SERVER_IP --bidir: 940 Mbps up, 16.5 Mbps down(Be sure to test all interfaces, noting any that are non-functional.)
GPU
glmark2-es2results:TODO: See this issue for discussion about a full suite of standardized GPU benchmarks.
Memory
tinymembenchresults:Click to expand memory benchmark result
``` tinymembench v0.4.10 (simple benchmark for memory throughput and latency) ========================================================================== == Memory bandwidth tests == == == == Note 1: 1MB = 1000000 bytes == == Note 2: Results for 'copy' tests show how many bytes can be == == copied per second (adding together read and writen == == bytes would have provided twice higher numbers) == == Note 3: 2-pass copy means that we are using a small temporary buffer == == to first fetch data into it, and only then write it to the == == destination (source -> L1 cache, L1 cache -> destination) == == Note 4: If sample standard deviation exceeds 0.1%, it is shown in == == brackets == ========================================================================== C copy backwards : 2901.5 MB/s (1.2%) C copy backwards (32 byte blocks) : 2900.6 MB/s C copy backwards (64 byte blocks) : 2894.8 MB/s C copy : 2509.5 MB/s (0.4%) C copy prefetched (32 bytes step) : 2887.2 MB/s C copy prefetched (64 bytes step) : 2883.8 MB/s (0.6%) C 2-pass copy : 1515.9 MB/s (0.2%) C 2-pass copy prefetched (32 bytes step) : 2346.4 MB/s (0.3%) C 2-pass copy prefetched (64 bytes step) : 2376.9 MB/s (0.3%) C fill : 3227.5 MB/s (1.2%) C fill (shuffle within 16 byte blocks) : 3225.9 MB/s (1.2%) C fill (shuffle within 32 byte blocks) : 3203.1 MB/s (0.8%) C fill (shuffle within 64 byte blocks) : 3152.5 MB/s (0.4%) NEON 64x2 COPY : 2855.8 MB/s (0.6%) NEON 64x2x4 COPY : 2854.5 MB/s NEON 64x1x4_x2 COPY : 2853.7 MB/s NEON 64x2 COPY prefetch x2 : 2838.9 MB/s NEON 64x2x4 COPY prefetch x1 : 2843.2 MB/s NEON 64x2 COPY prefetch x1 : 2842.5 MB/s NEON 64x2x4 COPY prefetch x1 : 2844.5 MB/s --- standard memcpy : 2831.0 MB/s standard memset : 3200.7 MB/s (0.8%) --- NEON LDP/STP copy : 2855.2 MB/s NEON LDP/STP copy pldl2strm (32 bytes step) : 2839.4 MB/s NEON LDP/STP copy pldl2strm (64 bytes step) : 2842.4 MB/s NEON LDP/STP copy pldl1keep (32 bytes step) : 2840.1 MB/s NEON LDP/STP copy pldl1keep (64 bytes step) : 2837.3 MB/s NEON LD1/ST1 copy : 2855.0 MB/s NEON STP fill : 3215.7 MB/s (0.8%) NEON STNP fill : 2373.0 MB/s (2.8%) ARM LDP/STP copy : 2856.0 MB/s ARM STP fill : 3224.5 MB/s (0.9%) ARM STNP fill : 2432.6 MB/s (2.4%) ========================================================================== == Framebuffer read tests. == == == == Many ARM devices use a part of the system memory as the framebuffer, == == typically mapped as uncached but with write-combining enabled. == == Writes to such framebuffers are quite fast, but reads are much == == slower and very sensitive to the alignment and the selection of == == CPU instructions which are used for accessing memory. == == == == Many x86 systems allocate the framebuffer in the GPU memory, == == accessible for the CPU via a relatively slow PCI-E bus. Moreover, == == PCI-E is asymmetric and handles reads a lot worse than writes. == == == == If uncached framebuffer reads are reasonably fast (at least 100 MB/s == == or preferably >300 MB/s), then using the shadow framebuffer layer == == is not necessary in Xorg DDX drivers, resulting in a nice overall == == performance improvement. For example, the xf86-video-fbturbo DDX == == uses this trick. == ========================================================================== NEON LDP/STP copy (from framebuffer) : 763.2 MB/s (0.6%) NEON LDP/STP 2-pass copy (from framebuffer) : 680.4 MB/s NEON LD1/ST1 copy (from framebuffer) : 836.6 MB/s NEON LD1/ST1 2-pass copy (from framebuffer) : 699.4 MB/s ARM LDP/STP copy (from framebuffer) : 578.4 MB/s (0.2%) ARM LDP/STP 2-pass copy (from framebuffer) : 549.3 MB/s (0.8%) ========================================================================== == Memory latency test == == == == Average time is measured for random memory accesses in the buffers == == of different sizes. The larger is the buffer, the more significant == == are relative contributions of TLB, L1/L2 cache misses and SDRAM == == accesses. For extremely large buffer sizes we are expecting to see == == page table walk with several requests to SDRAM for almost every == == memory access (though 64MiB is not nearly large enough to experience == == this effect to its fullest). == == == == Note 1: All the numbers are representing extra time, which needs to == == be added to L1 cache latency. The cycle timings for L1 cache == == latency can be usually found in the processor documentation. == == Note 2: Dual random read means that we are simultaneously performing == == two independent memory accesses at a time. In the case if == == the memory subsystem can't handle multiple outstanding == == requests, dual random read has the same timings as two == == single reads performed one after another. == ========================================================================== block size : single random read / dual random read 1024 : 0.0 ns / 0.0 ns 2048 : 0.0 ns / 0.0 ns 4096 : 0.0 ns / 0.0 ns 8192 : 0.0 ns / 0.0 ns 16384 : 0.0 ns / 0.0 ns 32768 : 0.0 ns / 0.0 ns 65536 : 5.7 ns / 8.9 ns 131072 : 8.6 ns / 11.9 ns 262144 : 12.3 ns / 15.8 ns 524288 : 14.2 ns / 18.1 ns 1048576 : 25.7 ns / 38.4 ns 2097152 : 80.2 ns / 115.9 ns 4194304 : 107.4 ns / 139.2 ns 8388608 : 128.2 ns / 160.1 ns 16777216 : 138.6 ns / 169.8 ns 33554432 : 144.0 ns / 175.1 ns 67108864 : 155.0 ns / 193.6 ns ```sbc-benchresultsPhoronix Test Suite
Results from pi-general-benchmark.sh: