Jump to content

How to super seed with a seedbox

From Pulsed Media Wiki


Super seeding is a technique for distributing large files quickly to many users by minimizing piece duplication across the swarm. Instead of uploading the same piece to multiple peers, the initial seeder sends each piece to a different peer, maximizing how fast the complete file spreads.

Pulsed Media customers have used this technique to distribute everything from software updates to large datasets across thousands of users. The method works the same way companies like Blizzard distribute game patches via BitTorrent: seed from multiple locations simultaneously, and the swarm does the rest.

This guide explains how to set up super seeding across multiple seedboxes for high-speed, high-volume distribution.

What you need

At minimum:

  • 1 fast seedbox as the origin node (SSD or NVMe storage recommended)
  • Multiple additional seedboxes as slave seeders (can be cheaper HDD-based boxes)

The more individual seedboxes you use, the better the distribution performance. Each box brings its own I/O, IP address, and network path, which means faster connections to new leechers.

Storage type depends on the data:

  • Small torrents with many peers: fast SSD/NVMe boxes work best
  • Large torrents (50+ GiB): HDD-based boxes with large capacity. See our M1000 or Storage Box plans.

We recommend using many shared slots rather than a few expensive dedicated servers. You get more discrete resources (IPs, disk I/O paths) per euro spent. For example: one SSD Seedbox as the source, then several 10Gbps Seedboxes as slaves.

Bandwidth calculation

Use this formula:

Total Data (MiB) / Time (seconds) = Required Bandwidth (MiB/s)

Example 1: 5 TiB in 1 week

5,242,880 MiB / 604,800 seconds = 8.7 MiB/s

One SSD seedbox handles this easily.

Example 2: 1,000 TiB in 1 week

1,048,576,000 MiB / 604,800 seconds = 1,734 MiB/s, roughly 20 Gbps.

On shared 10Gbps slots, expect around 10% sustained bandwidth per slot (about 110 MiB/s burst, 10 MiB/s after traffic limit). On 1Gbps dedicated servers, expect around 50% sustained (55 MiB/s).

For 1,000 TiB in a week, roughly 40 entry-level dedicated servers will do the job. Or a mix of shared and dedicated slots.

Step-by-step setup

1. Create the .torrent file

Use your preferred torrent client on the main (fast) seedbox to create the .torrent file. Add your tracker URLs and save it. This seedbox is the origin node that pushes data to the slaves.

2. Transfer the .torrent to all seedboxes

From the main seedbox, SCP the .torrent file to the watch folder on each slave:

scp file.torrent user@slave1.pulsedmedia.com:watch/
scp file.torrent user@slave2.pulsedmedia.com:watch/
scp file.torrent user@slave3.pulsedmedia.com:watch/

The watch folder auto-loads torrents on Pulsed Media seedboxes. Repeat for all your boxes.

Wait a few minutes after adding the first slave before adding the rest. This gives the first slave time to grab data from the origin, so the second wave of slaves can pull from both the origin and the first slave simultaneously.

3. Warm up the swarm

Monitor the swarm status as the slaves download. The combined download speed across all slaves should reach 2000+ MiB/s and accelerate as more slaves finish and start seeding.

It is normal for faster boxes to finish first. If a slow slave stalls, restarting its torrent client refreshes the peer list and often fixes it.

4. Release to the public

Once your seedbox cluster is mostly seeded (90%+ across all nodes), release the .torrent file to your audience.

Why wait? If users hit a slave that has not finished downloading, their speed drops or stalls at the last few percent. Waiting ensures a smooth experience.

Example: 10 GiB package, 1,000 users downloading immediately = 10 TiB of bandwidth demand. With a cluster of 40 boxes, expect initial burst speeds around 3,000 MiB/s for the first users. Speed decreases as fast peers finish and slow peers consume upload slots. Restart torrent clients on the slaves to re-boost when speeds drop.

Speeding things up further

More boxes with different networks and datacenter locations improve distribution. 10Gbps connections help for large initial bursts. Restarting slow clients refreshes peer lists and often recovers speed.

For content publishers distributing hundreds of terabytes to petabytes of data, Pulsed Media can help build a cost-effective seeding cluster. Contact sales@pulsedmedia.com for custom solutions including automated distribution scripting and swarm planning.

See also