Meilisearch and database imports can temporarily raise CPU/RAM use.
Large bookmark migrations.LinkAceのハードウェア要件：RAM、CPU、データベース、検索
RAM、CPU、MariaDB、Redis、Meilisearch、ブックマーク、Docker向けにLinkAceのハードウェアを計画し、実用的なZimaOSカスタムインストールの推奨事項を紹介します。
LinkAce requirements at a glance
LinkAce itself is lightweight, but the supported stable Docker path is a multi-service stack rather than one small container.
- RAM
- No numerical official minimum published. Stable Docker includes LinkAce, a database, Redis and Meilisearch, so whole-host RAM must cover all four.
- CPU
- No numerical official core minimum. Bookmark imports, indexing and search activity create the main bursts.
- Storage
- No universal official minimum. Bookmark data, search indexes, database files, logs and backups determine capacity.
- Database
- The stable Docker setup uses MariaDB by default; the quick local test can use SQLite but is not recommended for production.
- Search/cache
- Stable Compose bundles Meilisearch and Redis; Meilisearch can be removed if database search is preferred.
- Best Zima starting point
- ZimaBoard 2 832 is a strong all-in-one starting point for the stable stack; 16 GB gives more headroom for large imports and co-hosted services.
From official requirements to the right setup
Size LinkAce from the supported stable stack, not from the single-container SQLite test setup.
-
Official requirements
Use the stable Docker Compose path for a real installation. It includes LinkAce, MariaDB, Redis and Meilisearch.
-
Confirm your needs
Estimate bookmark count, import size and advanced-search use. Large imports and Meilisearch indexing create the more noticeable CPU/memory bursts.
-
Leave room to grow
If advanced Meilisearch search is unnecessary, use database search and remove the Meilisearch service to reduce the stack footprint.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with LinkAce's stable Compose configuration, persist the database/search/cache data, configure APP_URL and complete the post-install checklist.
Check every playback client
- Bookmark count
- Import size
- Meilisearch required
- MariaDB persistence
- Redis persistence
- Backup retention
- APP_URL/HTTPS
- Other ZimaOS services
Official minimum requirements
LinkAce's current documentation says it does not require a high-performance server, but it does not publish numerical CPU/RAM/disk minimums.
Do not invent a 1 GB or 2 GB official minimum. For production, budget for the complete stable Compose stack rather than the single-container SQLite evaluation setup.
| Requirement | Official minimum | What this supports |
|---|---|---|
| RAM minimum | No numerical official minimum published | Stable deployment includes multiple services. |
| CPU minimum | No numerical official minimum published | Imports and indexing drive bursts. |
| Storage minimum | No numerical official minimum published | Database, indexes and backups determine capacity. |
| Docker | Docker 19 or newer | Current stable Docker prerequisites. |
| Compose | Compose file version 3+ support | Current stable setup prerequisite. |
| Stable services | LinkAce + MariaDB + Meilisearch + Redis | Current supported Docker path. |
| Architectures | amd64, arm64 and arm/v7 | Current container support documented by LinkAce. |
When to upgrade your hardware
LinkAce should scale when search indexing, imports or the wider self-hosted stack creates sustained pressure.
Large imports or re-indexing consume memory
Search indexes and backups grow
Many other ZimaOS apps share the host
Meilisearch plus MariaDB creates more persistent data than the single-container test setup.
Long-running large bookmark libraries.LinkAce may remain light while the database/search stack competes with other services.
All-in-one productivity servers.Plan hardware growth with confidence
Scale LinkAce by simplifying or expanding the search/database stack based on real usage.
Use database search when Meilisearch is unnecessary
Removing Meilisearch reduces memory and persistent index overhead.
Useful on smaller all-in-one Zima hosts.Put MariaDB/search data on SSD
Fast durable storage improves indexing, search and backup responsiveness.
Use SATA/NVMe with ZimaBoard 2 or SSD tiers on ZimaCube 2.Move to 16 GB for larger multi-service stacks
Extra RAM helps MariaDB, Redis, Meilisearch and other apps coexist.
ZimaBoard 2 1664.Use ZimaCube when storage/backups become the priority
Larger local backups and broader productivity/NAS workloads can justify more capacity.
ZimaCube 2 Standard.Can it run on ZimaOS?
LinkAce is not currently confirmed as a public official one-click ZimaOS App Store page in the sources checked for this guide. It can be deployed through Install Custom App using LinkAce's stable Docker Compose setup.
Custom install LinkAce in ZimaOS
Use Install Custom App with LinkAce's stable Compose setup, persist MariaDB/Redis/Meilisearch data, and configure APP_URL plus secure service credentials.
Custom install LinkAce in the ZimaOS app ↗Use the supported stable Docker setup
The current stable path bundles LinkAce, MariaDB, Meilisearch and Redis for a real installation.
Review LinkAce Docker setup ↗Use database search if you want a lighter stack
LinkAce documents removing Meilisearch and switching APP_SEARCH_DRIVER to database when advanced search is unnecessary.
Review LinkAce search options ↗Choose Zima hardware for LinkAce
LinkAce is lightweight, but the stable four-service stack benefits from more RAM than the single-container test setup suggests.
Will you use the full stable MariaDB/Redis/Meilisearch stack or a lighter database-search setup?
Stable full stack
Use at least ZimaBoard 2 832; 16 GB gives more room for indexing and other apps.
- Best starting pointZimaBoard 2 832
- More stack headroomZimaBoard 2 1664
Large archive or broader productivity/NAS server
Use ZimaCube when backup/storage capacity matters more than LinkAce compute.
- Storage-first platformZimaCube 2 Standard
These are practical recommendations, not official bookmark-count or search-throughput tiers.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Normal LinkAce stable deployments. | LinkAce, MariaDB, Redis, Meilisearch and normal imports/search. |
|
8 GB is practical whole-stack headroom, not an official LinkAce minimum. | Get Now |
| ZimaBoard 2 1664 | Large bookmark libraries and broader productivity stacks. | More indexing/search memory plus additional containers. |
|
16 GB is most useful when Meilisearch and many other services share the host. | Get Now |
| ZimaCube 2 Standard | LinkAce as one app on a broader NAS/productivity server. | Bookmark services plus large backup retention and other storage workloads. |
|
Choose it for storage topology, not because LinkAce itself needs a six-bay NAS. | 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 LinkAce RAM, CPU, MariaDB, Redis, Meilisearch, Docker and ZimaOS deployment.
How much RAM does LinkAce need?
LinkAce does not publish a numerical official RAM minimum. The stable Docker setup includes the app, MariaDB, Redis and Meilisearch.
How many CPU cores does LinkAce need?
No numerical official core minimum is published. Imports and search indexing create the main CPU bursts.
Which database does LinkAce use?
The supported stable Docker setup uses MariaDB by default; the quick test setup can use SQLite but is not recommended for production.
Does LinkAce require Meilisearch?
No. The stable setup includes it for advanced search, but the docs explain how to remove it and use database search instead.
How much storage does LinkAce need?
No universal official disk minimum is published; database, search indexes, logs and backups determine capacity.
Does LinkAce need a GPU?
No dedicated GPU is required.
Can ZimaBoard 2 run LinkAce?
Yes. The 8 GB model is a strong starting point for the full stable Docker stack.
Which CPU architectures does LinkAce support?
Current container images support amd64, arm64 and arm/v7.
What sources informed this LinkAce hardware guide?
The guide uses LinkAce's current setup and Docker documentation plus current Zima product pages.
