Configuration matérielle requise pour Mylar3 : RAM, processeur, stockage et bibliothèque de bandes dessinées
Planifier le matériel Mylar3 pour la RAM, le CPU, les scans de bibliothèque de comics, les téléchargements, le stockage et des recommandations pratiques de déploiement de ZimaOS.
Mylar3 hardware requirements at a glance
Size Mylar3 from verified upstream requirements first, then add headroom for the actual workload and persistent data.
- RAM
- No numerical official minimum published
- CPU
- No numerical official minimum published
- Storage
- Comic files, download staging, metadata, and backups dominate capacity
- Runtime
- Python 3.8.1+ in current wiki guidance
- Optional dependency
- Unrar/winRAR for ComicTagger integration
- Best Zima starting point
- ZimaBoard 2 832
From official requirements to the right setup
Start with upstream facts for Mylar3, then size the workload instead of copying generic container labels.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- Comic library size
- Watchlist size
- Downloader integration
- ComicTagger use
- Archive extraction
- Post-processing
- Download staging
- Backup retention
Official minimum requirements
Upstream publishes Python and application dependencies but no numerical whole-host CPU, RAM, or disk minimum.
Do not use the ZimaOS listing's 64 MB memory label as an upstream minimum. Practical sizing is driven by the comic archive, download stack, and post-processing.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No numerical official minimum published | Tagging and post-processing drive CPU. | |
| No numerical official minimum published | Depends on library and integrations. | |
| At least 3.8.1 in current wiki guidance | Python 2 is unsupported. | |
| Required for ComicTagger integration | Must be available in the path or configured. | |
| Needed for full functionality | Without it functionality is limited. | |
| Not required | No GPU requirement. |
When to upgrade your hardware
Large scans
Archive growth
Automation stack pressure
Plan hardware growth with confidence
SSD config/cache
Keep Mylar3 application state on SSD.
SSDMore RAM
Useful for a larger multi-app automation host.
Higher-RAM hostComic storage
Use multi-bay storage for a large CBR/CBZ archive.
ZimaCube-class storageFaster CPU
Helps tagging and post-processing workloads.
Higher-throughput CPUCan it run on ZimaOS?
Install Mylar3 from the ZimaOS App Store
A specific public Mylar3 App Store page is available.
Open Mylar3 in the ZimaOS App Store ↗Follow Mylar3 installation guidance
Use the current project wiki for Python and ComicTagger dependencies.
Open Mylar3 installation instructions ↗Persist comics and app state
Keep comic libraries and application data on durable storage.
Open Mylar3 project guidance ↗Zima hardware for Mylar3
Mylar3 itself is lightweight; the comic library and downloader/post-processing stack determine hardware growth.
Choose by workload
Use ZimaBoard with real SATA storage.
Storage capacity and post-processing become more important.
ZimaOS store metadata is not treated as upstream official hardware guidance.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Light self-hosted services and small home-server workloads | Single-app or small multi-app deployments |
|
8 GB RAM and the 4-core N150 can constrain heavier game servers, large scans, and multi-service consolidation | Get Now |
| ZimaCube 2 Standard | Storage-heavy media, archives, downloads, and long retention | Large persistent data sets where drive bays matter more than peak CPU |
|
8 GB RAM can be lower than ZimaBoard 2 1664 for memory-heavy applications | Get Now |
| ZimaCube 2 Pro | CPU-heavier, higher-concurrency, and consolidated workloads | Game servers, repeated media scans, higher concurrency, or many demanding containers |
|
16 GB RAM can still constrain very large game or database 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
How much RAM does Mylar3 need?
Upstream does not publish a numerical whole-host RAM minimum.
How many CPU cores does Mylar3 need?
No numerical official CPU minimum is published.
Which Python version does Mylar3 require?
Current wiki guidance requires at least Python 3.8.1.
Does Mylar3 need Unrar?
Unrar or WinRAR is required for ComicTagger integration.
How much storage should I plan?
Size for CBR/CBZ files, download staging, metadata, and backups.
Can ZimaBoard 2 832 run Mylar3?
Yes for a typical personal library.
Does Mylar3 need a GPU?
No.
When should I choose ZimaCube 2?
For a large comic archive or CPU-heavier processing workflows.
