Netronomeのハードウェア要件：RAM、CPU、ストレージ、ネットワーク監視
RAM、CPU、iperf、速度テスト、保持期間、SQLite/PostgreSQL、そして実用的なZimaOS導入に向けてNetronomeハードウェアを計画する。
Netronome hardware requirements at a glance
Size Netronome from verified upstream requirements first, then add headroom for the actual workload and persistent data.
- RAM
- No numerical official minimum published
- CPU
- No numerical official minimum published
- Storage
- Persistent /data plus chosen database and history retention
- Database
- SQLite basic setup; PostgreSQL option for better performance
- Networking
- Network tests can intentionally consume substantial bandwidth
- Best Zima starting point
- ZimaBoard 2 832
From official requirements to the right setup
Start with upstream facts for Netronome, then size the workload instead of copying generic container labels.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- Test schedule
- iperf usage
- WAN/LAN speed
- SQLite vs PostgreSQL
- Retention period
- Packet-loss monitoring
- Tailscale integration
- Prometheus/other monitoring
Official minimum requirements
Upstream documents Docker, SQLite/PostgreSQL, network capabilities, and dependencies but no numerical whole-host CPU, RAM, or disk minimum.
Do not confuse network-test intensity with application baseline. Netronome itself is modest; iperf/speed tests can saturate links and PostgreSQL/retention can increase storage needs.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No numerical official minimum published | Network tests determine compute pressure. | |
| No numerical official minimum published | Depends on database and monitoring scale. | |
| ghcr.io/autobrr/netronome:latest | Documented in upstream Compose. | |
| 7575 | Default dashboard port. | |
| SQLite or PostgreSQL | PostgreSQL is documented for better performance. | |
| NET_RAW and NET_ADMIN where required | Needed for some network diagnostics. | |
| Not required | No GPU workload. |
When to upgrade your hardware
High-speed testing
Database growth
Monitoring expansion
Plan hardware growth with confidence
SSD database
Keep /data and database on SSD.
SSDMore RAM
Useful for PostgreSQL and a broader monitoring stack.
Higher-RAM hostRetention capacity
Add storage for longer test history.
Larger SSDFaster CPU/network
Useful for multi-gigabit iperf testing and many concurrent diagnostics.
Higher-throughput CPU plus 2.5/10GbECan it run on ZimaOS?
Install Netronome from the ZimaOS App Store
A specific public Netronome App Store page is available.
Open Netronome in the ZimaOS App Store ↗Use the official Netronome container
Upstream documents ghcr.io/autobrr/netronome:latest and Compose deployment.
Open Netronome repository ↗Choose SQLite or PostgreSQL deliberately
Use SQLite for a simple setup and PostgreSQL when scale/performance justifies it.
Review Netronome database options ↗Zima hardware for Netronome
Netronome's hardware needs are defined more by test throughput and data retention than by the dashboard itself.
Choose by workload
A ZimaBoard is sufficient with persistent SSD storage.
CPU, NIC speed, and PostgreSQL storage become more important.
Zima recommendations are workload-based; network tests can affect other traffic even when CPU/RAM remain low.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Light self-hosted services and small home-server workloads | Single-app or small multi-app deployments |
|
8 GB RAM and the 4-core N150 can constrain heavier game servers, large scans, and multi-service consolidation | Get Now |
| ZimaBoard 2 1664 | More containers, larger caches, and memory-heavier services | Single-app or small multi-app deployments |
|
CPU throughput is unchanged from the 832 model, so compute-heavy work can still be CPU-limited | Get Now |
| ZimaCube 2 Pro | CPU-heavier, higher-concurrency, and consolidated workloads | Game servers, repeated media scans, higher concurrency, or many demanding containers |
|
16 GB RAM can still constrain very large game or database workloads | 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
How much RAM does Netronome need?
Upstream does not publish a numerical whole-host RAM minimum.
How many CPU cores does Netronome need?
No numerical official CPU minimum is published.
Which database does Netronome use?
A basic Docker deployment can use SQLite; PostgreSQL is also documented for better performance.
What port does Netronome use?
The default dashboard port is 7575.
Which Docker image is used?
The upstream documentation uses ghcr.io/autobrr/netronome:latest.
Can ZimaBoard 2 832 run Netronome?
Yes for normal home network monitoring and scheduled tests.
Does Netronome need a GPU?
No.
When should I choose ZimaCube 2 Pro?
For multi-gigabit testing, higher monitoring concurrency, PostgreSQL-heavy retention, or broader consolidation.
