Measure broker CPU and network egress under fan-out, then check payload size, TLS and slow subscribers before adding cores.
Many clients subscribed to shared busy topics.Requisitos de hardware de Eclipse Mosquitto: RAM, CPU, almacenamiento y clientes MQTT, colas y persistencia
Planifica la CPU, la RAM, las conexiones de clientes MQTT, los mensajes en cola y la persistencia de Eclipse Mosquitto, con orientación práctica sobre el almacenamiento en Docker y el despliegue del broker en ZimaOS.
APP
Eclipse Mosquitto hardware requirements at a glance
Eclipse Mosquitto sizing depends on connected clients, publish rate, payload size, fan-out, QoS queues and persistence policy. The reviewed project and Docker Official Image docs publish no numerical whole-host minimum; commercial product figures do not define the community broker minimum.
- RAM
- No numerical official minimum published. Connections, subscriptions, retained messages and in-flight/offline queues consume memory; an enterprise product sizing claim is not a community minimum.
- CPU
- No numerical official minimum published. Publish frequency, subscriber fan-out, QoS, authentication and TLS drive compute beyond quiet idle usage.
- Storage
- Plan persistent retained/session/queue state, logs and backups. Durable data requires an enabled persistence mechanism and writable volume paths.
- Database / runtime
- A separate SQL server is not required for the standard broker. Traditional persistence writes a broker snapshot; the documented 2.1 SQLite plugin is an alternative, not a mandatory database.
- Ports / listeners
- 1883 is the conventional MQTT listener; TLS commonly uses 8883 when configured. WebSockets need an explicit listener. A port mapping does not create authentication or a listener by itself.
- Best Zima starting point
- ZimaBoard 2 832 is a practical small-home MQTT host with durable state. Choose more RAM or a stronger server only for measured broker pressure or companion workloads.
From official requirements to the right setup
Plan the complete Eclipse Mosquitto workload before selecting a server.
-
Official requirements
Use the Docker Official Image eclipse-mosquitto with a supported stable tag. Keep community broker facts separate from commercial broker editions and plugins.
-
Confirm your needs
Estimate simultaneous clients, messages per second, average payload, subscribers per topic, retained data and offline QoS queue growth. A single publisher can create substantial egress with large fan-out.
-
Leave room to grow
Choose one appropriate persistence mechanism and mount /mosquitto/config, /mosquitto/data and logs as required. Configure retention/queue limits and back up credentials/ACLs with durable state.
-
Run it on ZimaOS
Custom install in ZimaOS with a valid configuration file, explicit reachable listener and intended authentication. Map only configured ports to available host ports and make data paths writable to the container user.
Check every playback client
- Concurrent MQTT client connections
- Peak publish rate and average payload
- Subscribers per busy topic
- QoS and offline queue limits
- Retained message volume
- Persistence mode and writable data path
- Configured listener/authentication/TLS
- Log rotation and state recovery
Official minimum requirements
Checked on October 23, 2026 against official documentation and the project repository. Latest stable release observed: 2.1.2. Numerical requirements below retain their original scope.
No 128 MB or 1-core community minimum is inferred here. Bound retained data and offline queues, verify persistence behavior for your version, and benchmark the actual client/message/QoS pattern rather than treating connection count as the only sizing variable.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Host RAM | No numerical official minimum published. | Do not reuse RAM claims from commercial editions or example container limits. |
| CPU cores | No numerical official minimum published. | Fan-out, connection churn, QoS and TLS determine load. |
| Disk capacity | No numerical official minimum published. | Persistence state and logging policies determine storage. |
| Official image / architecture | Docker Official Image eclipse-mosquitto | Image documentation lists amd64 and ARM variants among supported platforms; use amd64 on Zima. |
| Persistence | Optional, explicitly configured | Traditional snapshot persistence and the 2.1 SQLite plugin are different modes; do not enable incompatible modes together. |
| SQL database | No external SQL service required for standard broker | The optional SQLite persistence plugin does not imply a mandatory PostgreSQL/MySQL service. |
| Directories / ports | /mosquitto/config, /mosquitto/data, /mosquitto/log; configured MQTT listener | 1883/8883/WebSocket ports must correspond to actual listeners and authentication settings. |
When to upgrade your hardware
Use observed Eclipse Mosquitto workload pressure to decide when an upgrade is warranted.
Delivery latency rises with publish bursts
Offline queues or retained state grow in memory
Persistence or logs pressure the disk
Review QoS delivery behavior, queue limits and disconnected clients. Additional memory postpones a limit but does not replace a bounded retention policy.
Persistent sessions and unreliable clients.Check snapshot/plugin mode, write latency, free space and log rotation. Preserve a tested restore path for broker state and credentials.
Long-lived brokers with heavy retained/queued data.Plan hardware growth with confidence
Address storage, memory, compute and deployment limits separately.
Use durable writable broker storage
Persist broker data and configuration with correct ownership, and verify state after a controlled restart.
ZimaBoard 2 with appropriate persistent storage or SATA SSD.Add memory for measured state and co-hosted apps
Choose 16 GB if actual resident state or companion workloads crowd the smaller host.
ZimaBoard 2 1664.Control queues and logs before expanding disk
Apply appropriate queue/persistence settings and log rotation, then size storage from measured state.
SSD capacity matched to the retention and write workload.Scale CPU/network for demonstrated fan-out
Test the intended publisher/subscriber pattern and TLS settings; a bigger server is justified only when measured processing or egress is the limit.
Stronger host or separated broker workload if needed.Can it run on ZimaOS?
No specific public official one-click Eclipse Mosquitto ZimaOS page was verified. Use Custom Install with the Docker Official Image and explicit broker configuration.
Custom install Eclipse Mosquitto in ZimaOS
Install eclipse-mosquitto, mount configuration and durable state, and map the configured MQTT/TLS listeners to available host ports. Preserve ACL/password files and use correct directory permissions.
Custom install Eclipse Mosquitto in the ZimaOS app ↗Use the official Eclipse Mosquitto deployment instructions
Keep the selected stable release, persistent paths and companion services aligned with upstream documentation.
Review Eclipse Mosquitto official installation ↗Use the Docker Official Image configuration
Review directory mounts, image tags and port mappings; a configuration file mount must point to the correct file or directory type.
Review Eclipse Mosquitto deployment details ↗Which Zima hardware fits Eclipse Mosquitto?
Start with the lowest reasonable host for the actual workload. Product specifications were checked against the current product pages.
Which workload best matches your Eclipse Mosquitto deployment?
Private home-automation MQTT broker
Use a modest always-on host with explicit listeners and persistence.
- Workload optionZimaBoard 2 832
MQTT alongside larger application services
Choose more memory for actual broker state and combined services.
- Workload optionZimaBoard 2 1664
These are practical workload recommendations, not official app requirements, compatibility certification, measured capacity limits or performance guarantees. Include all co-hosted services and independent backups.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Small private MQTT broker | Sensors, Zigbee2MQTT, Home Assistant and bounded persistent queues. |
|
No fixed client capacity is claimed; payload/fan-out/QoS can change demand sharply. | Get Now |
| ZimaBoard 2 1664 | Broker plus broader automation | More memory for retained state, configured queues and companion applications. |
|
Extra RAM does not fix an incorrect listener, missing authentication or a network bottleneck. | 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
Answers to Eclipse Mosquitto RAM, CPU, storage, Docker, database and ZimaOS sizing questions.
What is the Eclipse Mosquitto RAM minimum?
No numerical official minimum published. for the community broker in the reviewed sources. Connections, retained messages and offline/in-flight queues drive memory. Commercial product figures must keep their original scope.
How many CPU cores should an MQTT broker have?
No universal numerical core floor is published in the reviewed sources. Benchmark the intended publish rate, payload, TLS and subscriber fan-out instead of relying only on client count.
Does Mosquitto require MySQL or PostgreSQL?
No. The standard broker does not require an external SQL server. Traditional persistence and the newer optional SQLite persistence plugin are different approaches; select the supported configuration for your version.
How much disk space does MQTT persistence need?
Measure retained messages, persistent sessions, queued delivery state and logs. Configure limits and log rotation, leave working headroom and test recovery from the chosen persistence mechanism.
Does Mosquitto need a GPU?
No. Standard MQTT delivery uses CPU, memory, network and optional durable storage. The official container supports amd64 for Zima hardware; no GPU acceleration is required.
Can ZimaBoard 2 run Mosquitto?
It is a practical candidate for a modest private MQTT workload. Validate the actual traffic pattern, writable persistence paths and companion-service demand; do not interpret that recommendation as a guaranteed client maximum.
Why can clients fail even though Docker exposes port 1883?
The broker needs a listener bound appropriately inside the container and valid authentication/access settings. Port publishing alone does not configure those. Also check host conflicts, firewall rules and container networking.
When should I use ZimaCube 2?
Consider it for the broader combined server workload or measured broker pressure. A modest MQTT service alone does not justify multiple drive bays or dedicated GPU hardware.
What sources informed this Eclipse Mosquitto hardware guide?
Official project requirements, installation/configuration documentation, repository/release information and the current Zima product pages were checked on October 23, 2026. Practical hardware recommendations are editorial sizing guidance rather than upstream minimums.
