ITADN

Dell Pro Max with GB10 (NVIDIA Spark OEM model)

#92Opengeerlingguy 创建于 2025-11-21
G
geerlingguycommented
![Image](https://github.com/user-attachments/assets/43484921-44c4-4616-a683-f8777ca73eeb) ## Basic information - Board URL (official): https://www.dell.com/en-us/shop/desktop-computers/dell-pro-max-with-gb10/spd/dell-pro-max-fcm1253-micro/xcto_fcm1253_usx - Board purchased from: Provided by Dell, for testing - Board purchase date: November 19, 2025 - Board specs (as tested): NVIDIA GB10 / 128 GB LPDDR5x / 4TB NVMe SSD - Board price (as tested): $3998.99 ## Linux/system information ``` # output of `screenfetch` ./+o+- jgeerling@dell-gb10-1 yyyyy- -yyyyyy+ OS: Ubuntu 24.04 noble ://+//////-yyyyyyo Kernel: aarch64 Linux 6.14.0-1013-nvidia .++ .:/++++++/-.+sss/` Uptime: 34m .:++o: /++++++++/:--:/- Packages: 2339 o:+o+:++.`..```.-/oo+++++/ Shell: dash .:+o:+o/. `+sssoo+/ Disk: 36G / 3.6T (2%) .++/+:+oo+o:` /sssooo. CPU: ARM Cortex-X925 Cortex-A725 @ 20x 2.808GHz /+++//+:`oo+o /::--:. GPU: NVIDIA GB10 \+/+o+++`o++o ++////. RAM: 3806MiB / 122506MiB .++.o+++oo+:` /dddhhh. .+.o+oo:. `oddhhhh+ \+.++o+o``-````.:ohdhhhhh+ `:o+++ `ohhhhhhhhyo++os: .o:`.syhhhhhhh/.oo++o` /osyyyyyyo++ooo+++/ ````` +oo+++o\: `oo++. # output of `uname -a` Linux dell-gb10-1 6.14.0-1013-nvidia #13-Ubuntu SMP PREEMPT_DYNAMIC Wed Oct 29 06:01:19 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux ``` ## Benchmark results ### CPU - Geekbench 6: (3123 single / 19708 multi - https://browser.geekbench.com/v6/cpu/15161960) - 675.39 Gflops at 155W for **4.36 Gflops/W** ([geerlingguy/top500-benchmark](https://github.com/geerlingguy/top500-benchmark) [HPL result](https://github.com/geerlingguy/top500-benchmark/issues/79)) ### Power - Idle power draw (at wall): 31.5 W (1.3 W during shutdown, 38W with 200 Gbps link connected) - Maximum simulated power draw (`stress-ng --matrix 0`): 127.1 W - During Geekbench multicore benchmark: 114.8 W - During `top500` HPL benchmark: 155 W ### Disk #### ESL04TBTLCZ-27J4-TYN (Phison 4TB NVMe SSD) | Benchmark | Result | | -------------------------- | ------ | | iozone 4K random read | 80.51 MB/s | | iozone 4K random write | 409.89 MB/s | | iozone 1M random read | 3904.79 MB/s | | iozone 1M random write | 4938.67 MB/s | | iozone 1M sequential read | 3900.27 MB/s | | iozone 1M sequential write | 4955.19 MB/s | ### Network `iperf3` results: #### Built-in 200 Gbps ConnectX-7 - `iperf3 -c $SERVER_IP -P 4`: 106 Gbps - `iperf3 -c $SERVER_IP --reverse -P 4`: 106 Gbps - `iperf3 -c $SERVER_IP --bidir -P 10`: 86.3 Gbps up, 86.3 Gbps down #### Built-in 10 Gbps Ethernet (TODO) - `iperf3 -c $SERVER_IP`: TODO Gbps - `iperf3 -c $SERVER_IP --reverse`: TODO Gbps - `iperf3 -c $SERVER_IP --bidir`: TODO Gbps up, TODO Gbps down #### Built-in WiFi (MediaTek 7925 WiFi 7) - `iperf3 -c $SERVER_IP`: 672 Mbps - `iperf3 -c $SERVER_IP --reverse`: 694 Mbps - `iperf3 -c $SERVER_IP --bidir`: 498 Mbps up, 198 Mbps down ## GPU ### glmark2 `glmark2-es2` / `glmark2-es2-wayland` results: ``` 1. Install glmark2-es2 with `sudo apt install -y glmark2-es2` 2. Run `glmark2-es2` (with `DISPLAY=:0` prepended if running over SSH) 3. Replace this block of text with the results. ``` ### vkmark `vkmark` results: ``` 1. Install vkmark with `sudo apt install -y vkmark` 2. Run `vkmark` (with `DISPLAY=:0` prepended if running over SSH) 3. Replace this block of text with the results. ``` > **Note**: `vkmark` needs to be [compiled from source](https://github.com/geerlingguy/sbc-reviews/issues/76) on Debian 12 and earlier. ### GravityMark GravityMark results: ``` 1. Download the latest version of GravityMark: https://gravitymark.tellusim.com 2. Run `chmod +x [downloaded_filename].run` 3. Run `sudo ./[downloaded_filename].run` and press `y` to accept the terms. 4. Open the link it prints, and run the Benchmark defaults, changing to 720p resolution and 50,000 asteroids. ``` Note: These benchmarks require an active display on the device. Not all devices may be able to run `glmark2-es2`, so in that case, make a note and move on! ### AI / LLM Inference See: https://github.com/geerlingguy/ai-benchmarks/issues/34 ## Memory `tinymembench` results: <details> <summary>Click to expand memory benchmark result</summary> ``` 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 : 31501.5 MB/s (2.2%) C copy backwards (32 byte blocks) : 29732.9 MB/s C copy backwards (64 byte blocks) : 29696.7 MB/s C copy : 31632.6 MB/s C copy prefetched (32 bytes step) : 31485.7 MB/s C copy prefetched (64 bytes step) : 31360.6 MB/s (1.2%) C 2-pass copy : 20479.7 MB/s (0.1%) C 2-pass copy prefetched (32 bytes step) : 15752.1 MB/s (0.5%) C 2-pass copy prefetched (64 bytes step) : 15354.2 MB/s (0.5%) C fill : 61894.1 MB/s C fill (shuffle within 16 byte blocks) : 61766.8 MB/s C fill (shuffle within 32 byte blocks) : 61767.3 MB/s C fill (shuffle within 64 byte blocks) : 61793.8 MB/s NEON 64x2 COPY : 31847.2 MB/s (0.1%) NEON 64x2x4 COPY : 31939.7 MB/s NEON 64x1x4_x2 COPY : 31267.7 MB/s NEON 64x2 COPY prefetch x2 : 31126.2 MB/s (0.2%) NEON 64x2x4 COPY prefetch x1 : 31222.3 MB/s NEON 64x2 COPY prefetch x1 : 31200.8 MB/s NEON 64x2x4 COPY prefetch x1 : 31209.5 MB/s --- standard memcpy : 31937.3 MB/s standard memset : 86858.0 MB/s (1.6%) --- NEON LDP/STP copy : 31997.1 MB/s (0.2%) NEON LDP/STP copy pldl2strm (32 bytes step) : 31861.1 MB/s NEON LDP/STP copy pldl2strm (64 bytes step) : 32014.9 MB/s NEON LDP/STP copy pldl1keep (32 bytes step) : 31954.3 MB/s NEON LDP/STP copy pldl1keep (64 bytes step) : 31937.3 MB/s NEON LD1/ST1 copy : 31983.2 MB/s NEON STP fill : 86568.9 MB/s (5.1%) NEON STNP fill : 80447.6 MB/s (3.8%) ARM LDP/STP copy : 30950.4 MB/s (0.1%) ARM STP fill : 86267.4 MB/s (4.7%) ARM STNP fill : 77261.5 MB/s (1.1%) ========================================================================== == 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, [MADV_NOHUGEPAGE] 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 : 0.0 ns / 0.0 ns 131072 : 0.9 ns / 1.3 ns 262144 : 1.3 ns / 1.6 ns 524288 : 2.0 ns / 2.3 ns 1048576 : 2.6 ns / 3.0 ns 2097152 : 5.6 ns / 7.2 ns 4194304 : 10.2 ns / 13.3 ns 8388608 : 14.2 ns / 16.1 ns 16777216 : 26.1 ns / 35.0 ns 33554432 : 66.2 ns / 91.1 ns 67108864 : 91.9 ns / 112.4 ns block size : single random read / dual random read, [MADV_HUGEPAGE] 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 : 0.0 ns / 0.0 ns 131072 : 0.9 ns / 1.3 ns 262144 : 1.3 ns / 1.6 ns 524288 : 1.6 ns / 1.7 ns 1048576 : 1.7 ns / 1.8 ns 2097152 : 1.9 ns / 1.9 ns 4194304 : 8.5 ns / 11.8 ns 8388608 : 11.6 ns / 14.5 ns 16777216 : 13.4 ns / 15.8 ns 33554432 : 60.3 ns / 85.3 ns 67108864 : 86.3 ns / 106.7 ns ``` </details> ### Core to Core Memory Latency <img width="1920" height="1080" alt="Image" src="https://github.com/user-attachments/assets/7eeae90a-277e-4448-a338-f20b6af38480" /> ## `sbc-bench` results Run sbc-bench and paste a link to the results here: https://github.com/ThomasKaiser/sbc-bench/issues/127 ## Phoronix Test Suite Results from [pi-general-benchmark.sh](https://gist.github.com/geerlingguy/570e13f4f81a40a5395688667b1f79af): - pts/encode-mp3: 4.037 sec - pts/x264 1080p: 203.94 fps - pts/x264 4K: 52.84 fps - pts/phpbench: 1300604 - pts/build-linux-kernel (defconfig): 188.667 sec
12 条评论