Configuration matérielle requise pour Petio : RAM, processeur, stockage et MongoDB
Planifiez le matériel Petio pour la RAM, le CPU, MongoDB, les analyses de bibliothèque Plex et le volume de requêtes, avec des recommandations pratiques de déploiement sur ZimaOS.
Petio hardware requirements at a glance
Size Petio 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
- Petio config/logs plus MongoDB database and backups
- Database
- MongoDB 4.4 in official Docker docs
- Port
- 7777
- Best Zima starting point
- ZimaBoard 2 832 for a small Plex household; ZimaBoard 2 1664 for more DB headroom
From official requirements to the right setup
Start with upstream facts for Petio, then size the workload rather than copying generic container labels.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- Plex user count
- Request volume
- MongoDB size
- Plex library size
- Partial/full scan cadence
- Radarr/Sonarr integration
- Log retention
- Database backups
Official minimum requirements
Petio documents its Docker stack and MongoDB dependency but no numerical whole-host CPU, RAM, or disk minimum.
Do not size Petio like Plex Media Server. Petio does not perform the media transcoding; MongoDB, request volume, library scans, and integrations determine its own workload.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No numerical official minimum published | API and scheduled scans drive CPU. | |
| No numerical official minimum published | Petio and MongoDB share host memory. | |
| ghcr.io/petio-team/petio | Documented by Petio. | |
| MongoDB 4.4 | Local Mongo is used in the reference Compose. | |
| 7777 | Petio web service. | |
| Petio config/logs and MongoDB /data/db | Persist both. | |
| Not required | Petio itself does not transcode Plex media. |
When to upgrade your hardware
MongoDB growth
More users/requests
Host consolidation
Plan hardware growth with confidence
SSD MongoDB
Keep MongoDB on SSD.
SSD/NVMeMore RAM
Useful for MongoDB and a larger media-automation stack.
Higher-RAM hostBackup capacity
Keep MongoDB and Petio config backups separately.
Backup storageStronger CPU
Useful for a busier shared media-automation host.
Higher-throughput CPUCan it run on ZimaOS?
Install Petio from the ZimaOS App Store
A specific public Petio App Store page is available.
Open Petio in the ZimaOS App Store ↗Use Petio's documented Docker stack
Reference deployment uses Petio plus MongoDB 4.4.
Open Petio Docker docs ↗Separate Petio from Plex transcoding sizing
Petio is the request/discovery layer; Plex media workload is a different hardware calculation.
Review Petio architecture ↗Zima hardware for Petio
Petio is a database-backed companion app, not a media transcoder; MongoDB and the wider automation stack matter most.
Choose by workload
ZimaBoard 2 832 is a practical starting point.
More memory and CPU help the combined Petio/Mongo/integration workload.
Zima recommendations do not merge Plex transcoding requirements into Petio's hardware requirements.
| 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 database, extraction, OCR, and multi-service workloads | Get Now |
| ZimaBoard 2 1664 | More containers 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, database-heavier, and higher-concurrency workloads | Extraction, indexing, many users, or multiple demanding containers |
|
16 GB RAM can still constrain very large databases or local AI 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 Petio need?
Upstream does not publish a numerical whole-host RAM minimum.
How many CPU cores does Petio need?
No numerical official CPU minimum is published.
Which database does Petio use?
MongoDB; the official Docker guide uses MongoDB 4.4.
What port does Petio use?
7777.
Does Petio transcode Plex media?
No. Petio is a request/discovery/review companion app.
Can ZimaBoard 2 832 run Petio?
Yes for a small household setup.
Does Petio need a GPU?
No.
When should I use more RAM?
When MongoDB and the wider Plex automation stack need more cache/headroom.
