Dell Optiplex 780

[geerlingguy]

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: 37m
         .:++o:  /++++++++/:--:/-      Packages: 1683
        o:+o+:++.`..```.-/oo+++++/     Shell: bash 5.2.21
       .:+o:+o/.          `+sssoo+/    Resolution: 1920x1080
  .++/+:+oo+o:`             /sssooo.   DE: GNOME 46.7
 /+++//+:`oo+o               /::--:.   WM: Mutter
 \+/+o+++`o++o               ++////.   WM Theme: Adwaita
  .++.o+++oo+:`             /dddhhh.   GTK Theme: Yaru [GTK2/3]
       .+.o+oo:.          `oddhhhh+    Icon Theme: Yaru
        \+.++o+o``-````.:ohdhhhhh+     Font: Ubuntu Sans 11
         `:o+++ `ohhhhhhhhyo++os:      Disk: 12G / 220G (6%)
           .o:`.syhhhhhhh/.oo++o`      CPU: Intel Core2 Quad Q8400 @ 4x 2.66GHz
               /osyyyyyyo++ooo+++/     GPU: Quadro 2000
                   ````` +oo+++o\:     RAM: 1184MiB / 7813MiB

# 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: (360 single / 1045 multi - https://browser.geekbench.com/v6/cpu/14871481)
• 31.224 Gflops at 180W, for 0.17 Gflops/W (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): 139.9 W
• During Geekbench multicore benchmark: 99.9 W
• During top500 HPL benchmark: 180 W

Disk

KINGSTON SA400S37240G

Benchmark	Result
iozone 4K random read	28.17 MB/s
iozone 4K random write	66.05 MB/s
iozone 1M random read	234.36 MB/s
iozone 1M random write	250.09 MB/s
iozone 1M sequential read	244.45 MB/s
iozone 1M sequential write	249.74 MB/s

Network

iperf3 results:

• iperf3 -c $SERVER_IP: 938 Mbps
• iperf3 -c $SERVER_IP --reverse: 942 Mbps
• iperf3 -c $SERVER_IP --bidir: 825 Mbps up, 932 Mbps down

(Be sure to test all interfaces, noting any that are non-functional.)

GPU

glmark2

glmark2-es2 / glmark2-es2-wayland results:

=======================================================
    glmark2 2023.01
=======================================================
    OpenGL Information
    GL_VENDOR:      Mesa
    GL_RENDERER:    NVC3
    GL_VERSION:     OpenGL ES 3.1 Mesa 25.0.7-0ubuntu0.24.04.2
    Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=0 samples=0
    Surface Size:   800x600 windowed
=======================================================
[build] use-vbo=false: FPS: 879 FrameTime: 1.138 ms
[build] use-vbo=true: FPS: 2014 FrameTime: 0.497 ms
[texture] texture-filter=nearest: FPS: 1672 FrameTime: 0.598 ms
[texture] texture-filter=linear: FPS: 1664 FrameTime: 0.601 ms
[texture] texture-filter=mipmap: FPS: 1815 FrameTime: 0.551 ms
[shading] shading=gouraud: FPS: 1585 FrameTime: 0.631 ms
[shading] shading=blinn-phong-inf: FPS: 1595 FrameTime: 0.627 ms
[shading] shading=phong: FPS: 1586 FrameTime: 0.631 ms
[shading] shading=cel: FPS: 1589 FrameTime: 0.630 ms
[bump] bump-render=high-poly: FPS: 1177 FrameTime: 0.850 ms
[bump] bump-render=normals: FPS: 1917 FrameTime: 0.522 ms
[bump] bump-render=height: FPS: 1913 FrameTime: 0.523 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 1105 FrameTime: 0.905 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 679 FrameTime: 1.474 ms
[pulsar] light=false:quads=5:texture=false: FPS: 1231 FrameTime: 0.813 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 347 FrameTime: 2.890 ms
[desktop] effect=shadow:windows=4: FPS: 438 FrameTime: 2.288 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 258 FrameTime: 3.886 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 310 FrameTime: 3.229 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 322 FrameTime: 3.107 ms
[ideas] speed=duration: FPS: 170 FrameTime: 5.899 ms
[jellyfish] <default>: FPS: 662 FrameTime: 1.512 ms
[terrain] <default>: FPS: 73 FrameTime: 13.745 ms
[shadow] <default>: FPS: 1126 FrameTime: 0.889 ms
[refract] <default>: FPS: 91 FrameTime: 10.998 ms
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 2330 FrameTime: 0.429 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 2319 FrameTime: 0.431 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 1949 FrameTime: 0.513 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 2015 FrameTime: 0.496 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 2013 FrameTime: 0.497 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 2014 FrameTime: 0.497 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 2017 FrameTime: 0.496 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 2017 FrameTime: 0.496 ms
=======================================================
                                  glmark2 Score: 1298 
=======================================================

vkmark

vkmark results:

ERROR:             VkInstanceCreateInfo::pApplicationInfo::apiVersion has value of 0 which is not permitted. If apiVersion is not 0, then it must be greater than or equal to the value of VK_API_VERSION_1_0 [VUID-VkApplicationInfo-apiVersion]
=======================================================
    vkmark 2017.08
=======================================================
    Vendor ID:      0x10005
    Device ID:      0x0
    Device Name:    llvmpipe (LLVM 20.1.2, 128 bits)
    Driver Version: 1
    Device UUID:    32352e302e372d307562756e7475302e
=======================================================
[vertex] device-local=true: FPS: 96 FrameTime: 10.417 ms
[vertex] device-local=false: FPS: 97 FrameTime: 10.309 ms
[texture] anisotropy=0: FPS: 100 FrameTime: 10.000 ms
[texture] anisotropy=16: FPS: 94 FrameTime: 10.638 ms
[shading] shading=gouraud: FPS: 76 FrameTime: 13.158 ms
[shading] shading=blinn-phong-inf: FPS: 75 FrameTime: 13.333 ms
[shading] shading=phong: FPS: 66 FrameTime: 15.152 ms
[shading] shading=cel: FPS: 69 FrameTime: 14.493 ms
[effect2d] kernel=edge: FPS: 86 FrameTime: 11.628 ms
[effect2d] kernel=blur: FPS: 44 FrameTime: 22.727 ms
[desktop] <default>: FPS: 82 FrameTime: 12.195 ms
[cube] <default>: FPS: 110 FrameTime: 9.091 ms
[clear] <default>: FPS: 121 FrameTime: 8.264 ms
=======================================================
                                   vkmark Score: 85
=======================================================

Note: vkmark needs to be compiled from source 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:

System	CPU/GPU	Model	Eval Rate	Power (Peak)
Dell Optiplex 780 (Intel Q8400)	CPU	deepseek-r1:1.5b	2.30 Tokens/s	143 W
Dell Optiplex 780 (Intel Q8400)	CPU	llama3.2:3b	1.09 Tokens/s	146 W

More results: geerlingguy/ai-benchmarks#31

Memory

tinymembench results:

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                                     :   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 

Core to Core Memory Latency

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:

• pts/encode-mp3: 19.650 sec
• pts/x264 1080p: 14.36 fps
• pts/x264 4K: 3.38 fps
• pts/phpbench: 287754
• pts/build-linux-kernel (defconfig): 1016.956 sec

[geerlingguy]

Power consumption:

[geerlingguy]

(And yes, I know this is not an SBC, strictly speaking. Maybe I should change the name of this repo lol.)

[geerlingguy]

The main reason I'm testing this Core 2 Quad machine is because it seems to use the same dual-CPU-die design as the DC ROMA II mainboard I'm testing in #82.

According to TechPowerUp, it has a Die Size of 2x 82 mm².

And here's a delidded picture of the dies on a Q6600, courtesy of u/Kurtkrampmeier on r/overclocking: