TUTORIALS
Running a seedbox offshore, properly
A seedbox is a straightforward workload with a few counter-intuitive sizing decisions. The mistakes are almost always in the ratio between disk, bandwidth and memory, not in the software.
Sizing
- Disk is the constraint, not CPU. Two cores saturate a gigabit link comfortably. Buy capacity and worry about cores last.
- Match disk to what you actually retain. Two terabytes of active library on a gigabit port is a sane starting ratio; going wider on bandwidth without more disk buys you nothing.
- RAID-6 over RAID-0. The performance difference is invisible at these speeds and the failure difference is total.
- Memory matters more than expected. Every active piece consumes buffers; a large library on a small instance thrashes and the symptom looks like a slow disk.
Region
Latency is irrelevant here and throughput is everything, so take the strongest jurisdiction on offer. Chișinău and Victoria are the obvious choices; Sofia and Bucharest are excellent if most of your peers are European. Do not put this workload in Frankfurt, Singapore or Tokyo — those are our standard regions, local law applies normally, and the traffic profile is exactly the kind that attracts attention there.
Configuration that actually matters
- 01Cap global connectionsThousands of half-open connections exhaust file descriptors and make everything crawl. A few hundred active is plenty.
- 02Raise file-descriptor limitsThe default ulimit is far too low for this workload and the failure mode is silent stalling rather than an error.
- 03Preallocate filesIt costs a moment on creation and avoids severe fragmentation on a spinning array.
- 04Bind the client to the right interfaceOn a multi-address machine, an unbound client happily uses whichever address it feels like, which is rarely the one you intended.
Moving the data off
rsync over SSH is the default and it is fine. For large libraries, rclone against the S3-compatible endpoint is usually faster because it parallelises. Whatever you use, pull rather than push where possible — a pull from your own machine leaves the credentials at your end rather than on the box.
Published by NoDMCAVPS, an offshore host that files automated DMCA notices instead of forwarding them. What we still remove is listed in the acceptable use policy.
