Requisitos de hardware de PsiTransfer: RAM, CPU, almacenamiento y almacenamiento de cargas de archivos

Planifica el hardware de PsiTransfer para RAM, CPU, cargas simultáneas, retención de archivos, almacenamiento y recomendaciones prácticas de implementación en ZimaOS.

Requisitos de hardware de PsiTransfer: RAM, CPU, almacenamiento y almacenamiento de cargas de archivos

PsiTransfer hardware requirements at a glance

Size PsiTransfer 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
Upload files and retention dominate capacity
Docker
Official image: psitrax/psitransfer
Port
3000 by default
Best Zima starting point
ZimaBoard 2 832 for small sharing; ZimaCube for large retained uploads

From official requirements to the right setup

Start with upstream facts for PsiTransfer, then size the workload rather than copying generic container labels.

  1. Official requirements

  2. Confirm your needs

  3. Leave room to grow

  4. Run it on ZimaOS

Check every playback client

  • Max upload size
  • Concurrent uploads
  • Concurrent downloads
  • Retention period
  • /data capacity
  • Reverse proxy/TLS
  • Admin usage
  • Backup policy

Official minimum requirements

Upstream documents Docker and manual runtime but no numerical whole-host CPU, RAM, or disk minimum.

PsiTransfer upstream repository

Do not invent a server minimum from Node.js runtime requirements. Practical sizing follows concurrent transfers and how much uploaded data is retained at once.

RequirementOfficial minimumWhat this supports
No numerical official minimum publishedConcurrent transfers and TLS matter.
No numerical official minimum publishedDepends on concurrent traffic.
psitrax/psitransferRecommended upstream deployment.
3000Configurable.
/dataContainer data volume should be owned by UID 1000.
Node.js >= 12Not a host-RAM requirement.
Not requiredNo GPU workload.

When to upgrade your hardware

Large uploads

Transfer concurrency

Host contention

Plan hardware growth with confidence

Persistent upload storage

Use SATA SSD/HDD for /data.

SSD/HDD

More RAM

Useful for larger shared-host workloads.

Higher-RAM host

Large retention pool

Use ZimaCube for many or very large retained files.

Multi-bay storage

Faster network

Useful for heavy LAN file sharing.

2.5GbE/10GbE when justified

Can it run on ZimaOS?

Zima hardware for PsiTransfer

PsiTransfer itself is lightweight; file retention, concurrent transfers, and network/storage throughput determine hardware growth.

Choose by workload

Small personal/team file sharing

ZimaBoard is sufficient with external upload storage.

Large uploads or heavy LAN sharing

Storage capacity and network throughput become more important.

Zima recommendations are practical mappings, not upstream hardware certifications.

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
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 built-in discrete GPU
8 GB RAM and the 4-core N150 can constrain heavier database, extraction, OCR, and multi-service workloads Get Now
ZimaCube 2 Standard Storage-heavy libraries, downloads, PDFs, podcasts, and retained uploads Large persistent data sets where drive bays matter most
CPU
Intel Core i3-1215U
Memory
8 GB RAM
Storage
256 GB system storage, 6 HDD bays, SSD expansion
Network
Dual 2.5GbE
Acceleration
Storage and PCIe expansion
8 GB RAM can be lower than ZimaBoard 2 1664 for memory-heavy services Get Now
ZimaCube 2 Pro CPU-heavier, database-heavier, and higher-concurrency workloads Extraction, indexing, many users, or multiple demanding containers
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 and SSD expansion
16 GB RAM can still constrain very large databases or local 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 PsiTransfer need?

Upstream does not publish a numerical whole-host RAM minimum.

How many CPU cores does PsiTransfer need?

No numerical official CPU minimum is published.

Which Docker image does PsiTransfer use?

psitrax/psitransfer.

What port does PsiTransfer use?

3000 by default.

Where are uploaded files stored?

The official container uses /data.

Can ZimaBoard 2 832 run PsiTransfer?

Yes for small and moderate sharing workloads.

Does PsiTransfer need a GPU?

No.

When should I choose ZimaCube 2?

For large retained uploads, more drive capacity, or high-throughput file sharing.

What sources informed this guide?

This page uses current PsiTransfer Docker/project docs, its verified ZimaOS App Store page, and current Zima hardware specifications.