متطلبات العتاد لـ Bamboo: ذاكرة الوصول العشوائي (RAM)، ووحدة المعالجة المركزية (CPU)، والتخزين، وتزامن عمليات البناء
خطّط لمكونات Bamboo من حيث ذاكرة RAM ووحدة المعالجة المركزية وخطط البناء وقاعدة البيانات الخارجية والوكلاء والقطع الأثرية، مع توصيات عملية لنشر ZimaOS.
Bamboo hardware requirements at a glance
Size Bamboo from verified upstream requirements first, then add headroom for the actual workload and persistent data.
- RAM
- No universal minimum; small-team workload reference: 4 GB
- CPU
- No universal minimum; small-team workload reference: 4 cores
- Storage
- Bamboo home, artifacts, caches, logs, database, and backups
- Java
- Java 21 supported for Bamboo 12.1 server and agents
- Database
- H2 is evaluation-only; external database recommended for production
- Best Zima starting point
- ZimaBoard 2 1664 for a small controller; ZimaCube 2 Pro for local build-heavy use
From official requirements to the right setup
Start with current upstream facts for Bamboo, then size the workload rather than copying generic container or catalog labels.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- Plan count
- Concurrent builds
- Local vs remote agents
- Build memory
- Artifact retention
- Database engine
- Repository cache
- User count
Official minimum requirements
Atlassian does not publish one universal Bamboo CPU/RAM minimum because sizing depends on plan complexity and concurrency. It does publish workload-based hardware references.
The 4-core/4-GB small-team value is a best-practice scenario reference, not a universal minimum. Production should use an external database, and build-agent requirements must be sized separately.
| Requirement | Official minimum | What this supports |
|---|---|---|
| x86 / 64-bit x86-derived | Atlassian's supported server hardware family. | |
| 4 cores for individual/small-team scenario | Not a universal minimum. | |
| 4 GB for individual/small-team scenario | Not a universal minimum. | |
| Java 21 | Bamboo 12.1 server requires a supported full JDK. | |
| External database recommended | Bundled H2 is for evaluation and is more vulnerable to data loss on crashes. | |
| Local or remote agents | Build-resource demand depends on what runs on the agents. | |
| Not required | Only specific build/test jobs may independently require GPU. |
When to upgrade your hardware
Build queue/concurrency
Artifact/cache growth
Server/database pressure
Plan hardware growth with confidence
SSD Bamboo home/database
Use SSD for controller state, caches and database.
SSD/NVMeMore controller RAM
Useful for more plans/users and plugins.
ZimaBoard 2 1664 or higherArtifact capacity
Expand storage for retained builds and logs.
ZimaCube 2 StandardRemote build compute
Use stronger or separate build agents for heavy CI work.
Dedicated agents / ZimaCube 2 Pro-class computeCan it run on ZimaOS?
Custom install Bamboo in ZimaOS
No specific public official ZimaOS App Store page was verified, so this page uses the Custom Install route.
Custom install Bamboo in the ZimaOS app ↗Use the current Bamboo 12.1 platform matrix
Current Bamboo requires supported Java/database versions and an x86 server platform.
Open Bamboo supported platforms ↗Separate controller and agent sizing
Use the best-practice workload table as a reference and size build agents from actual jobs.
Open Bamboo sizing guidance ↗Zima hardware for Bamboo
Bamboo controller sizing and build-agent sizing must be separated. A small controller can fit modest hardware while build/test jobs may require much more compute.
Choose by workload
Use a 16 GB ZimaBoard for comfortable controller/database headroom.
Build CPU, RAM, artifact I/O and agent count dominate.
The Zima recommendation does not turn Atlassian workload examples into a universal minimum.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 1664 | Memory-heavier web, database, CI controller, and collaboration workloads | Moderate multi-container workloads |
|
CPU is still a 4-core N150; more RAM does not raise build or browser-execution throughput | Get Now |
| ZimaCube 2 Standard | Storage-heavy mail, repositories, attachments, and media | Large persistent datasets where drive bays matter most |
|
8 GB RAM can be less suitable than ZimaBoard 2 1664 for memory-heavy services | Get Now |
| ZimaCube 2 Pro | CPU-heavy CI, larger SQL/search workloads, and higher concurrency | Build orchestration, larger databases, and consolidated services |
|
16 GB RAM can still constrain very large enterprise or browser-grid 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
Does Bamboo publish one minimum RAM value?
No. Atlassian states that CPU and memory requirements depend on plan complexity and concurrency.
What does Atlassian list for a small-team workload?
The current best-practice table lists 4 cores and 4 GB RAM for an individual/small-team usage profile.
Which Java version does Bamboo 12.1 support?
Java 21 is supported, and the server needs a full JDK.
Can I use the bundled H2 database in production?
Atlassian recommends an external database for production; H2 is intended for evaluation.
What usually drives Bamboo hardware growth?
Concurrent builds, build complexity, agent workload, artifacts, caches, users and database activity.
Can ZimaBoard 2 1664 run a small Bamboo controller?
It is a practical controller starting point, especially when builds run on remote agents.
Does Bamboo itself need a GPU?
No. Individual CI jobs may independently require GPU hardware.
When should I choose ZimaCube 2 Pro?
For heavier local build execution, higher concurrency or broader CI consolidation.
