Dell Optiplex 780

[comment]: # (If desired, delete this line and add an image of the board here) ## Basic information - Board URL (official): https://i.dell.com/sites/csdocuments/Shared-Content_data-Sheets_Documents/en/us/optiplex_780_tech_spec_sheet.pdf - Board purchased from: eBay - Board purchase date: November 2025 - Board specs (as tested): 4GB RAM / 240 GB Kingston SSD / Core 2 Quad 2.66 GHz - Board price (as tested): $60 ## Linux/system information ``` # output of `screenfetch` ./+o+- jgeerling@optiplex-780 yyyyy- -yyyyyy+ OS: Ubuntu 24.04 noble ://+//////-yyyyyyo Kernel: x86_64 Linux 6.14.0-35-generic .++ .:/++++++/-.+sss/` Uptime: 2m .:++o: /++++++++/:--:/- Packages: 1642 o:+o+:++.`..```.-/oo+++++/ Shell: dash .:+o:+o/. `+sssoo+/ Disk: 9.9G / 220G (5%) .++/+:+oo+o:` /sssooo. CPU: Intel Core2 Quad Q8400 @ 4x 2.66GHz /+++//+:`oo+o /::--:. GPU: Quadro 2000 \+/+o+++`o++o ++////. RAM: 1008MiB / 7813MiB .++.o+++oo+:` /dddhhh. .+.o+oo:. `oddhhhh+ \+.++o+o``-````.:ohdhhhhh+ .++ .:/++++++/-.+sss/` `:o+++ `ohhhhhhhhyo++os: /+++//+:`oo+o /::--:. /osyyyyyyo++ooo+++/ yyyyy- -yyyyyy+ # output of `uname -a` Linux optiplex-780 6.14.0-35-generic #35~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Oct 14 13:55:17 UTC 2 x86_64 x86_64 x86_64 GNU/Linux ``` ## Benchmark results ### CPU - Geekbench 6: (TODO single / TODO multi - PASTE_URL) - TODO Gflops ([geerlingguy/top500-benchmark](https://github.com/geerlingguy/top500-benchmark) HPL result) ### Power - Idle power draw (at wall): 66 W (0.4W shut down) - Maximum simulated power draw (`stress-ng --matrix 0`): TODO W - During Geekbench multicore benchmark: 99.9 W - During `top500` HPL benchmark: TODO W ### Disk #### MANUFACTURER_AND_MODEL_OF_DISK_HERE [comment]: # (Run `lsblk -o NAME,FSTYPE,LABEL,MOUNTPOINT,SIZE,MODEL` to get model) | Benchmark | Result | | -------------------------- | ------ | | iozone 4K random read | TODO MB/s | | iozone 4K random write | TODO MB/s | | iozone 1M random read | TODO MB/s | | iozone 1M random write | TODO MB/s | | iozone 1M sequential read | TODO MB/s | | iozone 1M sequential write | TODO MB/s | ``` wget https://raw.githubusercontent.com/geerlingguy/pi-cluster/master/benchmarks/disk-benchmark.sh chmod +x disk-benchmark.sh sudo MOUNT_PATH=/ TEST_SIZE=1g ./disk-benchmark.sh ``` Run benchmark on any attached storage device (e.g. eMMC, microSD, NVMe, SATA) and add results under an additional heading. Also consider running [PiBenchmarks.com script](https://www.jeffgeerling.com/blog/2023/using-pibenchmarkscom-sbc-disk-performance-testing). ### Network `iperf3` results: - `iperf3 -c $SERVER_IP`: TODO Mbps - `iperf3 -c $SERVER_IP --reverse`: TODO Mbps - `iperf3 -c $SERVER_IP --bidir`: TODO Mbps up, TODO Mbps down (Be sure to test all interfaces, noting any that are non-functional.) ## 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 Basic `ollama` LLM model inference results: ``` # Install ollama curl -fsSL https://ollama.com/install.sh | sh # Download some models ollama pull llama3.2:3b \ && ollama pull llama3.1:8b \ && ollama pull llama2:13b # Download the benchmarking script git clone https://github.com/geerlingguy/ollama-benchmark.git cd ollama-benchmark # Run benchmark on multiple models declare -a models=("llama3.2:3b" "llama3.1:8b" "llama2:13b") for i in "${models[@]}"; do ./obench.sh -m "$i" -c 3 --markdown; done ``` Note that Ollama will run on the CPU if no valid GPU / drivers are present. Be sure to note whether Ollama runs on the CPU, GPU, or a dedicated NPU. ## 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 : 1854.7 MB/s C copy backwards (32 byte blocks) : 1853.1 MB/s C copy backwards (64 byte blocks) : 1855.1 MB/s (0.4%) C copy : 1854.8 MB/s C copy prefetched (32 bytes step) : 1866.4 MB/s C copy prefetched (64 bytes step) : 1864.3 MB/s C 2-pass copy : 1719.9 MB/s (0.2%) C 2-pass copy prefetched (32 bytes step) : 1784.5 MB/s (0.1%) C 2-pass copy prefetched (64 bytes step) : 1782.6 MB/s (0.4%) C fill : 2355.4 MB/s C fill (shuffle within 16 byte blocks) : 2355.4 MB/s C fill (shuffle within 32 byte blocks) : 2353.4 MB/s C fill (shuffle within 64 byte blocks) : 2355.6 MB/s --- standard memcpy : 3352.9 MB/s (0.1%) standard memset : 2355.1 MB/s --- MOVSB copy : 2042.5 MB/s (0.2%) MOVSD copy : 2039.2 MB/s SSE2 copy : 1864.4 MB/s SSE2 nontemporal copy : 3331.5 MB/s SSE2 copy prefetched (32 bytes step) : 1867.8 MB/s (0.2%) SSE2 copy prefetched (64 bytes step) : 1866.8 MB/s SSE2 nontemporal copy prefetched (32 bytes step) : 3362.1 MB/s (0.1%) SSE2 nontemporal copy prefetched (64 bytes step) : 3369.8 MB/s SSE2 2-pass copy : 1730.3 MB/s (9.4%) SSE2 2-pass copy prefetched (32 bytes step) : 1793.9 MB/s SSE2 2-pass copy prefetched (64 bytes step) : 1795.2 MB/s SSE2 2-pass nontemporal copy : 1603.6 MB/s (0.1%) SSE2 fill : 2356.4 MB/s SSE2 nontemporal fill : 6822.3 MB/s (0.2%) ========================================================================== == 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 : 2.3 ns / 3.5 ns 131072 : 3.8 ns / 5.0 ns 262144 : 4.6 ns / 5.6 ns 524288 : 5.0 ns / 5.9 ns 1048576 : 5.2 ns / 6.0 ns 2097152 : 9.0 ns / 12.8 ns 4194304 : 48.5 ns / 74.4 ns 8388608 : 69.2 ns / 96.2 ns 16777216 : 80.7 ns / 106.4 ns 33554432 : 86.9 ns / 110.8 ns 67108864 : 90.5 ns / 114.1 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 : 2.3 ns / 3.5 ns 131072 : 3.4 ns / 4.6 ns 262144 : 4.0 ns / 5.0 ns 524288 : 4.3 ns / 5.1 ns 1048576 : 4.5 ns / 5.1 ns 2097152 : 6.2 ns / 8.2 ns 4194304 : 45.5 ns / 68.8 ns 8388608 : 65.0 ns / 86.3 ns 16777216 : 74.9 ns / 92.6 ns 33554432 : 79.8 ns / 94.7 ns 67108864 : 82.6 ns / 97.0 ns ``` </details> ### Core to Core Memory Latency [comment]: # (If this is a new CPU/SoC, run c2clat to generate a core to core memory access latency graph: https://gist.github.com/geerlingguy/842974c0e49c201c28f4be54a05cc89c) TODO: Paste c2clat graph here. ## `sbc-bench` results Run sbc-bench and paste a link to the results here: ``` wget https://raw.githubusercontent.com/ThomasKaiser/sbc-bench/master/sbc-bench.sh sudo /bin/bash ./sbc-bench.sh -r ``` ## Phoronix Test Suite Results from [pi-general-benchmark.sh](https://gist.github.com/geerlingguy/570e13f4f81a40a5395688667b1f79af): - pts/encode-mp3: TODO sec - pts/x264 1080p: TODO fps - pts/x264 4K: TODO fps - pts/phpbench: TODO - pts/build-linux-kernel (defconfig): TODO sec