Default worker concurrency can raise memory use on multi-core systems.
Small servers running the full stack.Wymagania sprzętowe Funkwhale: pamięć RAM, procesor i pamięć masowa
Zaplanuj sprzęt dla Funkwhale pod kątem pamięci RAM, procesora, PostgreSQL, Redis, workerów Celery i pamięci na muzykę, z praktycznymi zaleceniami dotyczącymi niestandardowej instalacji ZimaOS.
Funkwhale requirements at a glance
Funkwhale is a multi-container music platform. Core sizing is driven by PostgreSQL, Redis, Celery workers, concurrent streaming and the size of the music/media library.
- RAM
- No numerical official minimum published. Upstream provides memory-saving settings because Celery spawns workers based on CPU cores by default.
- CPU
- No numerical official core minimum. Celery task concurrency and media processing scale with available CPU.
- Storage
- No universal official minimum. Music/media, PostgreSQL data, static/media files and backups dominate capacity.
- Database/cache
- The official deployment uses PostgreSQL and Redis; Celery handles asynchronous tasks.
- Docker
- Official Docker installation is supported and current docs target Funkwhale 2.0.x deployments.
- Best Zima starting point
- ZimaBoard 2 1664 is the safer compact all-in-one choice; ZimaCube 2 Standard/Pro is better once the music library or streaming workload grows.
From official requirements to the right setup
Size Funkwhale as a multi-service application plus a media library, not as a single lightweight web container.
-
Official requirements
Start with the official Docker Compose stack and budget for PostgreSQL, Redis, API/frontend and Celery services.
-
Confirm your needs
Estimate concurrent listeners plus background imports/scans. Celery worker concurrency defaults can increase memory use as CPU core count rises.
-
Leave room to grow
Plan music/media storage separately from application data; library capacity usually dominates long-term disk needs.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with Funkwhale's official Compose template, persist PostgreSQL/music/media data, and reduce Celery concurrency on limited hardware if needed.
Check every playback client
- Music library size
- Concurrent listeners
- Import/scan frequency
- PostgreSQL persistence
- Redis/Celery workload
- Media backup retention
- Reverse proxy/HTTPS
- Other ZimaOS services
Official minimum requirements
Funkwhale's current docs explain Docker/Debian prerequisites and memory optimization but do not publish one numerical hardware minimum.
Do not invent a 2 GB or 4 GB official minimum. The platform can be tuned down on limited devices, but worker count, database/cache and media storage determine practical sizing.
| Requirement | Official minimum | What this supports |
|---|---|---|
| RAM minimum | No numerical official minimum published | Memory varies with workers and service stack. |
| CPU minimum | No numerical official minimum published | Celery concurrency and background tasks use CPU. |
| Storage minimum | No numerical official minimum published | Music/media and PostgreSQL data determine capacity. |
| Database | PostgreSQL | Included in the official Docker stack. |
| Cache/task broker | Redis | Used for caching and Celery broker. |
| Memory tuning | CELERYD_CONCURRENCY can be reduced | Upstream documents lower worker concurrency and solo pool to reduce memory. |
When to upgrade your hardware
Funkwhale should scale when media capacity, listener concurrency or background tasks become persistent bottlenecks.
Celery workers create memory pressure
Concurrent streaming and imports increase
Music library and backups outgrow storage
More listeners plus scans/imports add network, CPU and database activity.
Shared or federated pods.Media files dominate capacity long before the application itself.
Large personal or community libraries.Plan hardware growth with confidence
Scale Funkwhale around music storage, database/cache memory and background worker concurrency.
Put PostgreSQL and metadata on SSD
Fast persistent storage improves database and task responsiveness.
Use SATA/NVMe on ZimaBoard 2 or SSD tiers on ZimaCube 2.Use 16 GB for an all-in-one pod
Extra memory helps API, PostgreSQL, Redis and Celery coexist.
ZimaBoard 2 1664.Use multi-drive storage for the music library
Large FLAC/lossless libraries benefit from expandable capacity.
ZimaCube 2 Standard.Use stronger CPU for more processing/concurrency
Additional CPU helps worker tasks and broader service consolidation.
ZimaCube 2 Pro.Can it run on ZimaOS?
Funkwhale 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 Funkwhale's official Docker Compose deployment.
Custom install Funkwhale in ZimaOS
Use Install Custom App with Funkwhale's official Compose template, persist PostgreSQL/music/media volumes, and configure hostname plus reverse proxy/HTTPS.
Custom install Funkwhale in the ZimaOS app ↗Use Funkwhale's official Docker deployment
Current administrator documentation supports a multi-container Docker Compose installation.
Review Funkwhale Docker installation ↗Reduce worker concurrency on limited hardware
Upstream documents CELERYD_CONCURRENCY and solo-pool tuning to reduce memory footprint.
Review Funkwhale memory optimization ↗Choose Zima hardware for Funkwhale
Funkwhale itself is moderate; music storage and the PostgreSQL/Redis/Celery stack drive the real decision.
Is this a small personal pod or a larger shared music library?
Small personal pod
Use 16 GB for the complete multi-container stack and SSD-backed metadata/database.
- Best compact choiceZimaBoard 2 1664
Large library or more listeners
Use ZimaCube for expandable media capacity and stronger general-purpose compute.
- Storage-first platformZimaCube 2 Standard
- Higher-headroom platformZimaCube 2 Pro
These are workload recommendations, not official listener-count guarantees.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 1664 | Personal or small-team Funkwhale pods. | API, PostgreSQL, Redis/Celery and moderate library/streaming. |
|
16 GB is practical headroom, not an upstream minimum. | Get Now |
| ZimaCube 2 Standard | Large music libraries. | Funkwhale plus multi-drive media storage and backups. |
|
Choose Standard mainly for storage; 8 GB may be less comfortable than 16 GB for the full service stack. | Get Now |
| ZimaCube 2 Pro | Larger shared pods and broader media-server use. | More listeners, workers, database/cache and multi-drive storage. |
|
Actual listener capacity depends on traffic, federation and media workload. | 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 Funkwhale RAM, CPU, PostgreSQL, Redis/Celery, music storage and ZimaOS deployment.
How much RAM does Funkwhale need?
Funkwhale does not publish a numerical official server RAM minimum.
How many CPU cores does Funkwhale need?
No numerical official minimum is published; Celery worker concurrency and imports affect CPU use.
Does Funkwhale use PostgreSQL?
Yes. PostgreSQL is part of the official Docker deployment.
Why does Funkwhale use Redis?
Redis is used for caching and as the Celery broker in the documented configuration.
How much storage does Funkwhale need?
No universal minimum; the music/media library and backups dominate disk usage.
Does Funkwhale need a GPU?
No dedicated GPU is required for normal music serving.
Can ZimaBoard 2 run Funkwhale?
Yes. The 16 GB model is the safer compact all-in-one choice for PostgreSQL, Redis and workers.
How can I reduce Funkwhale memory use?
Upstream documents reducing CELERYD_CONCURRENCY and using a solo pool for lower worker overhead.
What sources informed this Funkwhale hardware guide?
Current Funkwhale Docker, environment and memory-optimization documentation plus current Zima product pages.
