A 1GbE or 2.5GbE interface is a hard ceiling for a test intended to validate faster links.
Users upgrading to multigig switching or Wi-Fi.Configuration matérielle requise pour OpenSpeedTest : processeur, RAM et vitesse du réseau
Découvrez les exigences d’OpenSpeedTest en matière de processeur, de mémoire vive, de navigateur, de Docker, d’Ethernet 2,5 GbE et 10 GbE, puis choisissez le matériel ZimaOS adapté.
OpenSpeedTest requirements at a glance
OpenSpeedTest does not publish a numerical CPU or RAM minimum. Its official Docker implementation uses a lightweight unprivileged Alpine NGINX image, while the speed-test client runs in a web browser. For meaningful 1/2.5/10GbE testing, server NIC speed, client/browser performance and proxy/TLS overhead matter far more than the container footprint.
- CPU
- No numerical official minimum. CPU becomes relevant when pushing high browser-based throughput, TLS or many simultaneous tests.
- RAM
- No numerical official minimum. The official Docker image is intentionally lightweight.
- Client
- No plugin/software is required beyond a modern web browser; the client browser/CPU can itself become a bottleneck.
- Ports
- Official Docker defaults: HTTP 3000 and HTTPS 3001.
- Reverse proxy
- Official Docker docs warn that reverse proxies should allow about 35 MB POST bodies for the upload path.
- Best Zima starting point
- ZimaBoard 2 832 with dual 2.5GbE is a strong LAN speed-test host; use ZimaCube 2 Pro for a stock 10GbE server endpoint.
From official requirements to the right setup
OpenSpeedTest sizing starts from the network tier you want to measure.
-
Official requirements
Choose the target tier: 1GbE, 2.5GbE or 10GbE. The speed-test server cannot measure faster than its active NIC and switching path.
-
Confirm your needs
Check the browser/client device. A slow laptop, phone, Wi-Fi radio or browser JavaScript path can cap results even when the server is faster.
-
Leave room to grow
Avoid unnecessary reverse-proxy/TLS bottlenecks during baseline diagnostics. If a proxy is used, follow OpenSpeedTest's upload-body configuration guidance.
-
Run it on ZimaOS
Install OpenSpeedTest from ZimaOS, test a wired client with a known-good NIC/switch first, then compare Wi-Fi or other paths and upgrade only if the server endpoint is proven to be limiting.
Check every playback client
- Target 1/2.5/10GbE speed
- Server NIC link rate
- Switch link rate
- Client NIC or Wi-Fi capability
- Browser CPU/performance
- HTTP versus HTTPS
- Reverse-proxy POST body limit
- Concurrent speed-test clients
Official minimum requirements
OpenSpeedTest's official Docker project documents a lightweight NGINX container and browser client but no numerical CPU/RAM minimum.
A container that starts on tiny hardware can still give misleading results if its NIC, CPU or client browser cannot sustain the network speed being measured.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU | No numerical minimum published | Higher target throughput, TLS and concurrency can raise CPU demand. |
| RAM | No numerical minimum published | The image uses lightweight unprivileged Alpine NGINX. |
| HTTP port | 3000 | Current official Docker default. |
| HTTPS port | 3001 | Current official Docker default. |
| Client requirement | Web browser | No client-side plugin/software required. |
| Public Let's Encrypt setup | Public IPv4/IPv6 + resolving domain + email | Only for the documented public certificate path, not a private LAN test. |
When to upgrade your hardware
Upgrade OpenSpeedTest only when the test endpoint itself cannot sustain the network tier you want to measure.
The server NIC is below the target network speed
Browser/client CPU caps a multi-gigabit test
Reverse proxy/TLS becomes part of the bottleneck
Community multi-gig tests show that client hardware and browser performance can become the bottleneck before the server.
Users comparing 2.5GbE/10GbE across laptops and phones.OpenSpeedTest explicitly calls out upload-body requirements behind proxies, and TLS/proxy processing adds another layer to the measurement path.
Externally published or proxied test servers.Plan hardware growth with confidence
Improve measurement quality by removing bottlenecks from the path rather than allocating arbitrary RAM.
Use a wired reference client first
Validate server and switching capacity with a known-good wired client before diagnosing Wi-Fi.
This isolates Wi-Fi from server bottlenecks.Match the server NIC to the speed tier
ZimaBoard 2's dual 2.5GbE fits 1/2.5GbE testing, while a true 10GbE test needs a 10GbE server path.
ZimaCube 2 Pro is the current stock Zima 10GbE tier.Test direct before testing through a proxy
Direct access on ports 3000/3001 helps determine whether a reverse proxy or TLS layer depresses results.
Reintroduce the proxy after a direct baseline is known.Cross-check suspicious results with iperf3
OpenSpeedTest is browser-oriented; iperf3 is a dedicated network benchmark and can help isolate browser overhead.
Do this before replacing networking hardware.Can it run on ZimaOS?
OpenSpeedTest is currently available in the ZimaOS App Store under Networking.
Install OpenSpeedTest from ZimaOS
Use the packaged HTML5 speed-test server for LAN or remote testing.
Open OpenSpeedTest in the ZimaOS App StoreUse the current lightweight Docker path
The official image runs unprivileged Alpine NGINX and exposes ports 3000/3001.
Read OpenSpeedTest Docker documentationConfigure reverse proxies correctly
The official guide warns that proxy upload-body limits must support the speed-test upload path.
Read OpenSpeedTest self-hosted guidanceChoose Zima hardware for OpenSpeedTest
OpenSpeedTest is lightweight, but the server NIC determines which network tier it can meaningfully test.
What maximum LAN speed are you trying to measure?
Up to 2.5GbE
ZimaBoard 2's dual 2.5GbE makes it a natural lightweight endpoint.
- 1/2.5GbE LAN test serverZimaBoard 2 832
- Same endpoint plus more servicesZimaBoard 2 1664
10GbE LAN testing
Use a stock Zima tier with 10GbE rather than expecting a 2.5GbE NIC to measure 10GbE.
- 10GbE speed-test endpointZimaCube 2 Pro
No exact Mbps/Gbps result is guaranteed. Server NIC, switch, client NIC/Wi-Fi, browser CPU, TLS and proxy behavior all affect measured speed.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | A dedicated or shared 1/2.5GbE LAN speed-test endpoint. | Browser-based testing over dual 2.5GbE. |
|
Client/switch/browser can become the bottleneck before server compute. | Get Now |
| ZimaBoard 2 1664 | OpenSpeedTest on a larger networking/self-hosted server. | 2.5GbE testing plus more containers. |
|
16 GB does not improve the 2.5GbE NIC ceiling. | Get Now |
| ZimaCube 2 Pro | A real 10GbE-capable OpenSpeedTest server endpoint. | 10GbE LAN testing plus a larger networking/storage stack. |
|
10GbE does not guarantee a 10Gbps browser result; client and CPU path must also sustain it. | Get Now |
What the Press Says
Highlights from trusted reviewers worldwide.
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”Read full review
“The ZimaBoard 2 is a compact x86 server board that can be turned into a mini NAS, home server, media box, or self-hosting hub.”Read full review
“ZimaCube 2: A modern, high-performance NAS with plenty of room to grow—built for users who want more than basic storage.”Read full review
“Coverage focused on ZimaCube 2's open hardware foundation, no monthly fee, and self-hosting flexibility.”Read full review
Loved by the Community
Stories and reviews from people who build with Zima every day.
★★★★★
Zima Blade Little yet Powerful
Maybe I am not digital natives but I live with PCs since 12 years old in 1984 when IBM PC clone come to my home. Many years have passed and many operating system I've tried. For me Zima blade and CasaOS was a quantum leap for home PC enthusiast and server lab machine to make me stay curious and relevant for this era.
★★★★★
Very good!!
I use ZimaCube Pro as 5th Proxmox cluster node. It runs several VMs and containers, including a VM with GPU passthrough to run a self-hosted LLM. A specific LXC container runs a Samba server for NAS capabilities using four of six RAID 6 SATA HDDs with ZFS.
★★★★★
Great innovation for mini server!
It is very useful and makes a powerful mini server for many purposes, including university and college students in engineering and electronics. Thank you so much for making this server.
★★★★★
Avaliação ZimaBoard 2
Construí um servidor de uso pessoal. O desempenho está muito bom e funciona perfeitamente onde quer que eu esteja. A surpresa é não dependermos de grandes estruturas para termos nosso próprio servidor de dados. Como iniciante, estou gostando bastante do ZimaOS, pois ele é simples e eficiente.
Frequently asked questions
FAQ topics follow query fan-out around RAM, 2.5GbE/10GbE testing, browser limitations, reverse proxies and OpenSpeedTest versus iperf3.
How much RAM does OpenSpeedTest need?
OpenSpeedTest does not publish a RAM minimum. Its official Docker image is a lightweight NGINX-based container.
Can OpenSpeedTest measure 2.5GbE on ZimaBoard 2?
Yes, provided the server, switch and client all negotiate and sustain 2.5GbE.
Can stock ZimaBoard 2 measure a 10GbE path?
Not through its built-in 2.5GbE ports. A true 10GbE test needs a 10GbE server interface/path.
Why is OpenSpeedTest slower than iperf3?
OpenSpeedTest runs through a browser/application path while iperf3 is a dedicated network benchmark; browser/client CPU and proxy/TLS overhead can make results differ.
Can the client computer be the bottleneck?
Yes. Multi-gig browser tests can be limited by a weak client CPU, browser or NIC before the server is saturated.
Does OpenSpeedTest write test data to disk?
Normal use is designed as a network/browser benchmark rather than a disk benchmark, so disk throughput should not be interpreted as the measured resource.
Why does OpenSpeedTest fail behind my reverse proxy?
The official Docker docs warn that the proxy should allow roughly 35 MB POST bodies for the upload test path.
Can ZimaBoard 2 832 run OpenSpeedTest?
Yes. Its compute is far beyond the lightweight container's needs; the dual 2.5GbE ports are the more relevant specification.
What sources and further reading informed this OpenSpeedTest hardware guide?
Official Docker and self-hosted docs define the browser client, ports, lightweight NGINX image and proxy requirement. Reddit/home-networking discussions were used for multi-gig client-bottleneck fan-out; ZimaOS confirms the current Networking app.
