More simultaneous users increase API work and database connections.
Teams moving from small-group analytics to shared BI dashboards.متطلبات الأجهزة لتشغيل Metabase: ذاكرة الوصول العشوائي (RAM)، ووحدة المعالجة المركزية (CPU)، وقاعدة البيانات، والتزامن
حدّد موارد Metabase من حيث ذاكرة RAM ووحدة المعالجة المركزية PostgreSQL والمستخدمين المتزامنين ولوحات المعلومات وعمليات المزامنة الخلفية، مع توصيات عملية للتثبيت المخصص على ZimaOS.
Metabase requirements at a glance
Metabase publishes clear production sizing guidance and requires a durable application database for production.
- Application baseline
- At least 1 CPU core and 1 GB RAM for the Metabase application.
- Concurrent users
- For every 20 concurrent users, add about 1 CPU core and 2 GB RAM to the application.
- Application database
- Production should use a dedicated database, preferably PostgreSQL; start around 1 CPU core and 2 GB RAM.
- Database concurrency
- As a general rule, add about 1 CPU core and 1 GB RAM to PostgreSQL for every 40 concurrent users.
- Storage
- No universal disk minimum; application DB size and IOPS, logs and plugins determine storage needs.
- Best Zima starting point
- ZimaBoard 2 832 is ample for a small team; use 16 GB or ZimaCube 2 Pro as concurrency and background jobs grow.
From official requirements to the right setup
Metabase sizing is driven by concurrent interactive users plus background work such as syncs, scans, alerts and subscriptions.
-
Official requirements
Start with 1 CPU core and 1 GB RAM, then add roughly 1 CPU and 2 GB RAM for every 20 concurrent users.
-
Confirm your needs
Size the application database separately. Metabase recommends PostgreSQL and suggests a 1 CPU/2 GB starting point, adding roughly 1 CPU/1 GB per 40 concurrent users.
-
Leave room to grow
Add headroom for real dashboards, syncs, scans, X-Rays, subscriptions and alerts because asynchronous work can add CPU and memory pressure.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with the official Metabase container and a persistent PostgreSQL application database. Do not use H2 for production.
Check every playback client
- Peak concurrent users
- Dashboard card complexity
- Connected database count
- Sync/fingerprinting jobs
- Alerts/subscriptions
- Dedicated PostgreSQL app DB
- App DB IOPS/backups
- Other ZimaOS services
Official minimum requirements
Metabase publishes production-oriented CPU/RAM formulas rather than one fixed server size.
The 1 core/1 GB app baseline is official, but production sizing must also include the separate application database and concurrency growth.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Application baseline | 1 CPU core, 1 GB RAM | Current production baseline. |
| Application scaling | +1 CPU core and +2 GB RAM per 20 concurrent users | Current production guidance. |
| App database start | 1 CPU core, 2 GB RAM | Starting point for the application database server. |
| App database scaling | +1 CPU core and +1 GB RAM per 40 concurrent users | General PostgreSQL app-database rule. |
| Production database | PostgreSQL recommended | MySQL/MariaDB also work; H2 should be avoided in production. |
| Storage minimum | No universal numerical minimum published | Watch app-database disk usage and IOPS. |
When to upgrade your hardware
Scale when concurrency, background jobs or application-database latency pushes the service beyond its current envelope.
Concurrent dashboards approach the next tier
CPU stays high and operations queue
Application database latency becomes visible
Insufficient CPU can queue operations, increase memory use and destabilize the app.
Instances with complex dashboards, scans, X-Rays or many data sources.Slow app-DB response or IOPS can make Metabase feel unresponsive even when Java has free memory.
Production installations with growing metadata and dashboards.Plan hardware growth with confidence
Scale by keeping the application database fast and increasing CPU/RAM in line with observed concurrency.
Use PostgreSQL for production metadata
Move off H2 and back up the database that stores dashboards, questions, users and configuration.
Run PostgreSQL on SSD-backed storage.Increase app CPU/RAM by concurrency
Use the +1 CPU/+2 GB per 20 concurrent users formula as the starting rule.
ZimaBoard 2 1664 is a compact step-up for more BI users.Protect database IOPS
When app-DB storage queues I/O, requests can slow even when CPU/RAM look adequate.
Use SSD/NVMe for PostgreSQL.Scale horizontally when one instance becomes connection-limited
Metabase recommends multiple instances for larger populations instead of relying only on vertical scaling.
Plan shared app DB, load balancing and failure handling before scaling out.Can it run on ZimaOS?
Metabase is not currently presented as a verified public one-click ZimaOS App Store page. It can be deployed through Install Custom App using the official Docker image plus PostgreSQL.
Custom install Metabase in ZimaOS
Use Install Custom App with metabase/metabase and PostgreSQL. Set MB_DB_* credentials, persist PostgreSQL data, expose port 3000 or a reverse proxy, and back up the app DB.
Custom install Metabase in the ZimaOS app ↗Use the official Metabase Docker image
Metabase publishes an official Docker image and documents a production path using a durable application database.
Review Metabase Docker deployment ↗Do not keep H2 for production
H2 is intended for local demos; production installations should use PostgreSQL or another production-ready supported database.
Review Metabase application database guidance ↗Choose Zima hardware for Metabase
Metabase maps naturally to concurrency tiers. Small teams fit ZimaBoard 2 easily; stronger CPU and 16 GB RAM help as dashboard concurrency and background jobs rise.
Is this a small BI team or a higher-concurrency analytics service?
Solo user or small team
8 GB leaves large headroom over the 1 core/1 GB app baseline plus a small PostgreSQL app DB.
- Best starting pointZimaBoard 2 832
- More concurrency headroomZimaBoard 2 1664
Higher concurrency or broader analytics stack
Use stronger CPU and 16 GB RAM with SSD-backed PostgreSQL.
- Higher-headroom platformZimaCube 2 Pro
These recommendations are not query-latency guarantees; source-database performance and dashboard complexity can dominate.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Small Metabase teams and internal dashboards. | Metabase app, PostgreSQL app DB and light sync jobs. |
|
Query speed still depends heavily on the connected data warehouse and app-DB IOPS. | Get Now |
| ZimaBoard 2 1664 | More concurrent Metabase users and background jobs. | Metabase, PostgreSQL, alerts, subscriptions and additional analytics services. |
|
16 GB does not compensate for a slow source database or poor dashboard queries. | Get Now |
| ZimaCube 2 Pro | Higher-concurrency Metabase and broader BI consolidation. | More simultaneous dashboards, heavier syncs/scans, PostgreSQL and co-hosted services. |
|
Large deployments may be better served by multiple Metabase instances and a shared production app DB. | 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
These answers cover Metabase RAM, CPU, PostgreSQL, concurrency and ZimaOS deployment.
How much RAM does Metabase need?
Metabase recommends at least 1 GB RAM for the application baseline, plus about 2 GB more for every 20 concurrent users. The production application database needs its own resources.
How many CPU cores does Metabase need?
Start with at least 1 CPU core, then add roughly 1 CPU core for every 20 concurrent users. The application database should also start around 1 CPU core.
Can Metabase run on 2 GB RAM?
Yes for a small installation, but production must include both the Metabase Java process and its durable application database, so a 2 GB whole-host budget leaves little room.
Does Metabase need PostgreSQL?
Metabase strongly recommends PostgreSQL for the production application database. MySQL/MariaDB can also work; H2 is for demos.
How much storage does Metabase need?
There is no universal disk minimum. Application-database size, logs, plugins and IOPS matter more than a fixed capacity number.
Does Metabase need a GPU?
No dedicated GPU is required for normal dashboards, SQL queries or BI administration.
Can ZimaBoard 2 run Metabase?
Yes. The 8 GB model is already well above the small-team baseline and can also host a modest PostgreSQL app database on SSD-backed storage.
When should I upgrade Metabase hardware?
Upgrade when concurrent use moves into the next 20-user tier, CPU or memory remains heavily utilized, or the application database becomes slow or IOPS-bound.
What sources informed this Metabase hardware guide?
Current Metabase production, Docker and app-database documentation were used with current Zima product pages for hardware matching.
