event/scan volume, target size, policy/rule evaluation, retention and concurrent tasks Time the job and identify CPU, storage or external-service waits before replacing hardware.
Imports, processing and simultaneous users.Configuration matérielle requise pour SonarQube : RAM, processeur, stockage, portée de l’analyse et workers d’exécution
Planifiez la mémoire vive, le processeur, le stockage persistant et les dépendances de service de SonarQube, en dimensionnant ZimaOS selon la charge de travail, avec des sauvegardes et des choix matériels pratiques.
SonarQube hardware requirements at a glance
Automated code quality and security analysis This concerns the selected SonarQube server edition and release, including the supported Java/search/database topology. Code analysis scanners/build workers run separately; verify kernel/process limits and memory for search instead of treating a JVM heap option as whole-host RAM.
- RAM
- The linked SonarQube Server 2026.4 guide lists 4 GB RAM for its small-scale starting configuration and 16 GB for large-scale roles. The database and analysis/build workers require separate planning.
- CPU
- The same guide lists 2 cores for small-scale and 8 for large-scale roles. Match the selected edition/release and required host/kernel settings.
- Storage
- The small-scale starting figure is 30 GB, with at least 10% free disk space. Code volume, search/indexing, database storage and backups determine real capacity; the guide recommends monitoring and adjusting.
- Required services
- Use the supported upstream runtime and complete SonarQube deployment for the selected release. This concerns the selected SonarQube server edition and release, including the supported Java/search/database topology. Code analysis scanners/build workers run separately; verify kernel/process limits and memory for search instead of treating a JVM heap option as whole-host RAM.
- Main sizing variable
- event/scan volume, target size, policy/rule evaluation, retention and concurrent tasks
- Practical Zima starting point
- Conditional lab, data-storage or supporting-service hardware only; a complete production deployment requires a separately verified host meeting the upstream requirements. This concerns the selected SonarQube server edition and release, including the supported Java/search/database topology. Code analysis scanners/build workers run separately; verify kernel/process limits and memory for search instead of treating a JVM heap option as whole-host RAM.
From official requirements to the right setup
Plan the complete SonarQube workload before selecting a server.
-
Official requirements
Choose the exact edition, stable release and supported container/runtime. Use the supported upstream runtime and complete SonarQube deployment for the selected release. This concerns the selected SonarQube server edition and release, including the supported Java/search/database topology. Code analysis scanners/build workers run separately; verify kernel/process limits and memory for search instead of treating a JVM heap option as whole-host RAM.
-
Confirm your needs
Test a representative busy operation: event/scan volume, target size, policy/rule evaluation, retention and concurrent tasks Record peak resident memory, CPU, disk latency and completion time, including other containers.
-
Leave room to grow
Place active state on reliable persistent storage. Persist policies, signatures or rule data where used, configuration and retained logs/results. Budget working space for an upgrade or import and test recovery before relying on the deployment.
-
Run it on ZimaOS
Follow the supported upstream runtime, operating system and complete service topology for the selected release. On ZimaOS, consider Custom Install only when a maintained compatible amd64 image and every required host capability have been verified. Otherwise use a separately supported Linux environment; this guide does not certify an unverified container deployment. This concerns the selected SonarQube server edition and release, including the supported Java/search/database topology. Code analysis scanners/build workers run separately; verify kernel/process limits and memory for search instead of treating a JVM heap option as whole-host RAM.
Check every playback client
- Exact edition and stable release
- Supported upstream runtime and architecture
- All required companion services
- Realistic peak activity
- Persistent data and file ownership
- Free host ports and reachable URLs
- Working space and backup retention
- Successful database/file restore
Official minimum requirements
Reviewed November 11, 2026 against the linked upstream deployment documentation. Numerical values retain their stated minimum, recommendation or example scope; select release-compatible instructions before installation.
This concerns the selected SonarQube server edition and release, including the supported Java/search/database topology. Code analysis scanners/build workers run separately; verify kernel/process limits and memory for search instead of treating a JVM heap option as whole-host RAM. Numerical examples above retain their stated deployment scope; co-hosted services and independent backups need additional capacity.
| Requirement | Official minimum | What this supports |
|---|---|---|
| RAM guidance | The linked SonarQube Server 2026.4 guide lists 4 GB RAM for its small-scale starting configuration and 16 GB for large-scale roles. The database and analysis/build workers require separate planning. | Official guidance keeps its original test, recommendation or example scope. |
| CPU guidance | The same guide lists 2 cores for small-scale and 8 for large-scale roles. Match the selected edition/release and required host/kernel settings. | Core counts do not predict a fixed user, device or document capacity. |
| Storage planning | The small-scale starting figure is 30 GB, with at least 10% free disk space. Code volume, search/indexing, database storage and backups determine real capacity; the guide recommends monitoring and adjusting. | Installation space is separate from retained content, working files and backups. |
| Service topology | Use the supported upstream runtime and complete SonarQube deployment for the selected release. This concerns the selected SonarQube server edition and release, including the supported Java/search/database topology. Code analysis scanners/build workers run separately; verify kernel/process limits and memory for search instead of treating a JVM heap option as whole-host RAM. | Include every stateful companion service in the host budget. |
| Persistent state | Persist policies, signatures or rule data where used, configuration and retained logs/results. | An image rebuild or container replacement is not a backup. |
| Deployment boundary | This concerns the selected SonarQube server edition and release, including the supported Java/search/database topology. Code analysis scanners/build workers run separately; verify kernel/process limits and memory for search instead of treating a JVM heap option as whole-host RAM. | Check the linked project instructions for the selected edition and release. |
When to upgrade your hardware
Use observed SonarQube workload pressure to decide when an upgrade is warranted.
Busy operations exceed the available window
The complete stack runs short of memory
Persistent data approaches available capacity
Inspect the application and each required service for OOM events, sustained swap or growing queues. Reduce unnecessary concurrency before adding capacity.
Shared hosts and background work.Persist policies, signatures or rule data where used, configuration and retained logs/results. Track primary state and backup retention separately.
Long-lived installations and growing collections.Plan hardware growth with confidence
Address storage, memory, compute and deployment limits separately.
Use suitable active storage
Put latency-sensitive application/database state on durable local SSD storage and keep recoverable copies.
SATA or PCIe SSD according to measured data growth.Add memory for the complete stack
Choose a higher-RAM host when peak application and companion-service usage leaves inadequate OS headroom.
ZimaBoard 2 1664 or ZimaCube 2 Pro according to the measured constraint.Separate capacity from compute
A multi-drive system helps when retained content and backup storage are the problem; it is not automatically a faster application.
ZimaCube 2 when a broader multi-drive workload justifies it.Fix the observed bottleneck
This concerns the selected SonarQube server edition and release, including the supported Java/search/database topology. Code analysis scanners/build workers run separately; verify kernel/process limits and memory for search instead of treating a JVM heap option as whole-host RAM.
Check service configuration, I/O and network behavior before selecting a stronger CPU.Can it run on ZimaOS?
Follow the supported upstream runtime, operating system and complete service topology for the selected release. On ZimaOS, consider Custom Install only when a maintained compatible amd64 image and every required host capability have been verified. Otherwise use a separately supported Linux environment; this guide does not certify an unverified container deployment.
Verify the supported upstream deployment
This concerns the selected SonarQube server edition and release, including the supported Java/search/database topology. Code analysis scanners/build workers run separately; verify kernel/process limits and memory for search instead of treating a JVM heap option as whole-host RAM. Follow the supported upstream runtime, operating system and complete service topology for the selected release. On ZimaOS, consider Custom Install only when a maintained compatible amd64 image and every required host capability have been verified. Otherwise use a separately supported Linux environment; this guide does not certify an unverified container deployment.
Review upstream deployment guidance ↗Use the official SonarQube deployment instructions
Keep the selected stable release, persistent paths and companion services aligned with upstream documentation.
Review SonarQube official installation ↗Check workload-specific deployment details
This concerns the selected SonarQube server edition and release, including the supported Java/search/database topology. Code analysis scanners/build workers run separately; verify kernel/process limits and memory for search instead of treating a JVM heap option as whole-host RAM.
Review SonarQube deployment details ↗Which Zima hardware fits SonarQube?
Conditional lab, data-storage or supporting-service hardware only; a complete production deployment requires a separately verified host meeting the upstream requirements.
Which workload best matches your SonarQube deployment?
Conditional lab, data-storage or supporting-service hardware only; a complete production deployment requires a separately verified host meeting the upstream requirements. This concerns the selected SonarQube server edition and release, including the supported Java/search/database topology. Code analysis scanners/build workers run separately; verify kernel/process limits and memory for search instead of treating a JVM heap option as whole-host RAM.
- Supporting hardware onlyZimaBoard 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 1664 | Conditional lab or supporting-service role | event/scan volume, target size, policy/rule evaluation, retention and concurrent tasks |
|
Conditional lab, data-storage or supporting-service hardware only; a complete production deployment requires a separately verified host meeting the upstream requirements. This concerns the selected SonarQube server edition and release, including the supported Java/search/database topology. Code analysis scanners/build workers run separately; verify kernel/process limits and memory for search instead of treating a JVM heap option as whole-host RAM. | Get Now |
| ZimaCube 2 Pro | Conditional lab or supporting-service role | Use the supported upstream runtime and complete SonarQube deployment for the selected release. This concerns the selected SonarQube server edition and release, including the supported Java/search/database topology. Code analysis scanners/build workers run separately; verify kernel/process limits and memory for search instead of treating a JVM heap option as whole-host RAM. |
|
Conditional lab, data-storage or supporting-service hardware only; a complete production deployment requires a separately verified host meeting the upstream requirements. This concerns the selected SonarQube server edition and release, including the supported Java/search/database topology. Code analysis scanners/build workers run separately; verify kernel/process limits and memory for search instead of treating a JVM heap option as whole-host RAM. | 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 SonarQube RAM, CPU, storage, Docker, database and ZimaOS sizing questions.
How much RAM should I plan for SonarQube?
The linked SonarQube Server 2026.4 guide lists 4 GB RAM for its small-scale starting configuration and 16 GB for large-scale roles. The database and analysis/build workers require separate planning. Include ZimaOS, the application and its companion services rather than reserving the entire machine for one container.
What drives the CPU requirement?
The same guide lists 2 cores for small-scale and 8 for large-scale roles. Match the selected edition/release and required host/kernel settings. The workload to test is: event/scan volume, target size, policy/rule evaluation, retention and concurrent tasks
Which data must survive a container update?
Persist policies, signatures or rule data where used, configuration and retained logs/results. Preserve a consistent database/file set and verify that your recovery procedure restores a working application.
What other services belong in the budget?
Use the supported upstream runtime and complete SonarQube deployment for the selected release. This concerns the selected SonarQube server edition and release, including the supported Java/search/database topology. Code analysis scanners/build workers run separately; verify kernel/process limits and memory for search instead of treating a JVM heap option as whole-host RAM.
Does this workload need a dedicated GPU?
A dedicated GPU is not assumed for the core workflow described here. Optional AI, acceleration or media-processing integrations must be evaluated separately against the selected backend.
Can I deploy it on ZimaOS?
Follow the supported upstream runtime, operating system and complete service topology for the selected release. On ZimaOS, consider Custom Install only when a maintained compatible amd64 image and every required host capability have been verified. Otherwise use a separately supported Linux environment; this guide does not certify an unverified container deployment. This concerns the selected SonarQube server edition and release, including the supported Java/search/database topology. Code analysis scanners/build workers run separately; verify kernel/process limits and memory for search instead of treating a JVM heap option as whole-host RAM.
What should I check before upgrading hardware?
This concerns the selected SonarQube server edition and release, including the supported Java/search/database topology. Code analysis scanners/build workers run separately; verify kernel/process limits and memory for search instead of treating a JVM heap option as whole-host RAM. Measure the same representative operation before and after a configuration or hardware change.
Which Zima device is a practical starting point?
Conditional lab, data-storage or supporting-service hardware only; a complete production deployment requires a separately verified host meeting the upstream requirements. This concerns the selected SonarQube server edition and release, including the supported Java/search/database topology. Code analysis scanners/build workers run separately; verify kernel/process limits and memory for search instead of treating a JVM heap option as whole-host RAM.
What sources informed this SonarQube hardware guide?
This guide was reviewed against the linked project deployment documentation on November 11, 2026. Zima device choices are editorial workload guidance, separate from upstream requirements and measured performance.


