High memory usage on a seedbox is usually normal it does not mean something is broken.
High RAM usage is often healthy
Torrent clients and media apps cache data in memory to run faster, and Linux deliberately uses spare RAM for disk caching rather than leaving it idle. So a seedbox showing most of its memory “in use” is typically working exactly as intended.
Each account has a memory allowance
Every seedbox account runs within a fair share of the server’s memory so that one account’s load can’t slow down its neighbours. If the apps on your account try to use more than that share, the system stops one of them to protect the rest of the server (an “out-of-memory” stop). You would see this as a client suddenly closing, or as a transfer that runs fast for a few seconds, then stalls or times out, then resumes — especially during heavy activity.
What most often pushes an account over its allowance
Memory-heavy applications are the usual cause, particularly when several run at once:
- Docker containers — the daemon and its containers carry real memory overhead.
- Deduplicating backups (Borg, restic) with a large repository — the deduplication cache is memory-heavy and grows with the backup size.
- Large database dumps or restores — these can spike memory well above their steady state.
- Many simultaneous transfers, connections, or a media-library scan running at the same time as the above.
What to do if apps keep getting stopped
The honest fix is to give your account the memory your workload needs. If your setup genuinely needs to run these applications, the right answer is more memory, not a smaller setup:
- Add Extra RAM to this service from your control panel’s Upgrade Options. It raises your account’s memory allowance directly, with no migration — best when your working set is modestly over your current allowance.
- Move to a higher-RAM plan if your full concurrent workload needs more headroom than the add-on covers. Open a ticket and tell us roughly what you run at the same time, and we’ll point you to the right fit.
If you would rather keep your current plan, you can instead ease the load — run fewer heavy jobs at once, let one media-library scan finish before starting another, or avoid running Docker and a large backup at the same time. That keeps you inside the allowance, but it means shrinking what you run; if you want to actually run the full workload, the memory upgrade is the path that fixes it.
There’s nothing you need to “fix” about normal high RAM usage — it’s only worth acting on if apps are actually being stopped.
