Requisitos de hardware do Crucible: RAM, CPU, armazenamento e repositórios de revisão de código

Planeie o hardware do Crucible para CPU, RAM, indexação do repositório, E/S da cache local, utilização da base de dados e recomendações práticas de implementação do ZimaOS.

Requisitos de hardware do Crucible: RAM, CPU, armazenamento e repositórios de revisão de código

Crucible hardware requirements at a glance

Size Crucible from verified upstream requirements first, then add headroom for workload and persistent data.

RAM
1 GB minimum; 2 GB headroom
CPU
1.8 GHz or higher; single core sufficient
Storage
Fast local disk strongly recommended
Database
Bundled HSQLDB is evaluation-only
Architecture
x86/x86-64 officially supported
Best Zima starting point
ZimaBoard 2 832

From official requirements to the right setup

Start with current upstream facts for Crucible, then size the real workload instead of generic container labels.

  1. Official requirements

  2. Confirm your needs

  3. Leave room to grow

  4. Run it on ZimaOS

Check every playback client

  • Users/concurrency
  • CPU workload
  • RAM headroom
  • Database/runtime
  • Persistent storage
  • Network
  • Backups
  • Upgrade path

Official minimum requirements

Official upstream requirements for Crucible are summarized below.

Atlassian Crucible supported platforms

Keep software/runtime limits separate from whole-host sizing unless upstream explicitly publishes host hardware minimums.

RequirementOfficial minimumWhat this supports
1.8 GHz or higherSingle core sufficient.
1 GB2 GB provides headroom.
512 MBSize within host RAM.
Fast local diskNFS/SAN unsupported for cache.
x86/x86-64Supported hardware family.
External DB for productionHSQLDB evaluation-only.
Not requiredNo GPU workload.

When to upgrade your hardware

Higher concurrency

State growth

Host contention

Plan hardware growth with confidence

SSD application state

Keep databases and active app state on SSD.

SSD/NVMe

More RAM

Add memory for database/cache/workers and multi-app hosts.

Higher-memory Zima model

More capacity

Expand content, attachment, report, or backup storage.

ZimaCube storage

Stronger CPU

Use higher CPU throughput for heavier dynamic workloads.

ZimaCube 2 Pro

Can it run on ZimaOS?

Zima hardware for Crucible

Choose hardware based on the verified workload, not app-store memory metadata.

Choose by workload

Small or baseline deployment

Use the smallest Zima option that clears official/runtime needs.

Growing or heavier deployment

Scale CPU, RAM, and storage based on the dominant bottleneck.

Recommendations are practical mappings, not upstream hardware certifications unless explicitly stated.

Zima hardware Best for Example workload Core configuration Recommended boundary Next step
ZimaBoard 2 832 Light self-hosted services Small single-app or multi-app workloads
CPU
Intel N150, 4 cores, up to 3.6 GHz
Memory
8 GB LPDDR5
Storage
32 GB eMMC plus 2x SATA 3.0 and PCIe 3.0 expansion
Network
Dual 2.5GbE
Acceleration
PCIe expansion; no discrete GPU
8 GB RAM can limit heavier Java, search, helpdesk, and AI stacks Get Now
ZimaBoard 2 1664 Memory-heavier services Moderate databases and multi-container workloads
CPU
Intel N150, 4 cores, up to 3.6 GHz
Memory
16 GB LPDDR5
Storage
64 GB eMMC plus 2x SATA 3.0 and PCIe 3.0 expansion
Network
Dual 2.5GbE
Acceleration
PCIe expansion; no discrete GPU
CPU remains the 4-core N150 Get Now
ZimaCube 2 Pro CPU-heavy and database-heavy workloads Large repositories, helpdesk stacks, reporting, and AI orchestration
CPU
Intel Core i5-1235U, 10 cores / 12 threads
Memory
16 GB RAM
Storage
256 GB system storage, 6 HDD bays, up to 4 SSD slots
Network
10GbE + 2.5GbE
Acceleration
Higher CPU throughput plus PCIe/SSD expansion
16 GB RAM can still be low for large enterprise or AI workloads Get Now

What the Press Says

Highlights from trusted reviewers worldwide.

La Razón
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”
Read full review
GameRevolution
“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
TechRadar Pro
“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
FOX 8
“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.

ZimaBlade single-board server
★★★★★

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.

ZimaCube Pro personal cloud
★★★★★

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.

ZimaBlade single-board server
★★★★★

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.

ZimaBoard 2 single-board 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 Crucible need?

1 GB minimum; 2 GB headroom.

How much CPU does Crucible need?

1.8 GHz or higher; single core sufficient.

What storage should I plan?

Fast local disk strongly recommended.

Which database or runtime matters most?

Bundled HSQLDB is evaluation-only.

Does it need a GPU?

No GPU is required for the base application unless the upstream workload explicitly adds a separate accelerated component.

Can Zima hardware run it?

ZimaBoard 2 832.

What usually triggers an upgrade?

Higher concurrency, database growth, storage growth, or heavier processing.

What should be backed up?

Persistent application data, databases, configuration, and workload-specific content.

What sources informed this guide?

Current upstream requirements/deployment documentation and current Zima hardware specifications.