Requisitos de hardware do MySpeed: RAM, CPU, armazenamento e histórico de testes de velocidade

Planeie o hardware do MySpeed para RAM, CPU, testes de velocidade agendados, retenção de resultados, débito de rede e implementação prática no ZimaOS.

Requisitos de hardware do MySpeed: RAM, CPU, armazenamento e histórico de testes de velocidade

MySpeed hardware requirements at a glance

Size MySpeed 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
Small database/history footprint that grows with retention
Networking
Internet throughput is the first sizing variable
Integrations
Prometheus and Grafana supported
Best Zima starting point
ZimaBoard 2 832

From official requirements to the right setup

Start with upstream facts for MySpeed, then size the workload instead of 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

  • Test interval
  • Speed-test provider
  • WAN speed
  • Retention period
  • Multiple servers
  • Prometheus/Grafana use
  • Notification integrations
  • Other containers

Official minimum requirements

Upstream documents features and deployment but no numerical whole-host CPU, RAM, or disk minimum.

MySpeed upstream repository

Do not over-size MySpeed. The most important operational effect is that scheduled tests consume real network bandwidth; retention and integrations matter more than raw application memory.

RequirementOfficial minimumWhat this supports
No numerical official minimum publishedTest clients and scheduling determine load.
No numerical official minimum publishedThe dashboard itself is lightweight.
Fully configurableHistory can be kept from days to indefinitely.
Ookla, LibreSpeed, CloudflareProvider selection changes testing behavior.
Prometheus and Grafana supportedCan externalize time-series analysis.
Not requiredNo GPU workload.

When to upgrade your hardware

Frequent tests

WAN saturation

Long retention

Plan hardware growth with confidence

SSD app state

Keep MySpeed data on reliable persistent storage.

SSD

More RAM

Only useful if the host runs many other monitoring apps.

Higher-RAM host

Longer retention

Add storage if keeping long history or external monitoring data locally.

Larger SSD

Faster network

Relevant only when the host NIC itself limits very fast internet tests.

2.5GbE/10GbE when WAN speed justifies it

Can it run on ZimaOS?

Zima hardware for MySpeed

MySpeed is lightweight; network scheduling and retention are more important than CPU or RAM.

Choose by workload

Normal home speed monitoring

A ZimaBoard easily handles the application.

Very fast WAN or broader monitoring stack

Choose hardware for NIC capacity and other monitoring services.

Zima recommendations are practical workload mappings, not upstream minimums.

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 game servers, large scans, and multi-service consolidation Get Now
ZimaBoard 2 1664 More containers, larger caches, and memory-heavier services Single-app or small multi-app deployments
CPU
Intel N150, 4 cores, up to 3.6 GHz
Memory
16 GB LPDDR5
Storage
64 GB eMMC plus 2x SATA 3.0 and PCIe 3.0 expansion
Network
Dual 2.5GbE
Acceleration
PCIe expansion; no built-in discrete GPU
CPU throughput is unchanged from the 832 model, so compute-heavy work can still be CPU-limited Get Now
ZimaCube 2 Pro CPU-heavier, higher-concurrency, and consolidated workloads Game servers, repeated media scans, higher concurrency, or many 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 game or database 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 MySpeed need?

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

How many CPU cores does MySpeed need?

No numerical official CPU minimum is published.

Which speed-test providers can MySpeed use?

The project supports Ookla, LibreSpeed, and Cloudflare.

Can MySpeed retain results indefinitely?

Yes. Retention is configurable from short periods to forever.

Does MySpeed support Prometheus and Grafana?

Yes.

Can ZimaBoard 2 832 run MySpeed?

Yes for normal home monitoring.

Does MySpeed need a GPU?

No.

When should I use stronger Zima hardware?

Only when very fast networking or a broader monitoring stack justifies it.

What sources informed this guide?

This page uses the current MySpeed repository, its verified ZimaOS App Store page, and current Zima hardware specifications.