How to super seed with a seedbox

How to super seed with a seedbox?

Abstract

This super seeding article is about seeding the maximum amount of data, in the least possible time by utilizing seedboxes, instead of the traditional "superseed" of consecutive blocks being seeded. Here we show you how the get the maximum amount of data into the swarm, to serve thousands of users simultaneously.

We are going to use a multitude of seedboxes to achieve this.

Who is this target for?

Content publishers, tracker maintainers etc. People who need their data swiftly to as many users as possible. For example, Blizzard releases updates via Bittorrent, and they see a huge spike of traffic upon new releases, the only concern is getting as much of it out as possible as fast as possible, not just a single source of seed like traditional "superseed" is targeted to be.

This actually does not differ that much from what Blizzard does.

What's needed

You need multiple seedboxes in order to do this, at the very least you need 1 very fast, and multiple "slave seeders". You can work with a few upto dozens or even hundreds*.

The type of seedboxes depends upon your budget, the idea behind using many is to get as many discreet I/O resources, IPs etc. involved as possible, all of these instances will have differing timings etc. ensuring faster to connect speeds to new downloaders (leechers).

• ) Ask support to help distribute your .torrent file to the hundreds of boxes, it should be scripted.

Recommendation of resources

We recommend using many of our shared slots, this way you get access to as many discreet resources as possible with the least amount of money - you don't necessarily need a big budget cluster of dedicated servers.

For example, get a few 2012 slots for the initial fast seeds, then a bunch of 2009+, Value or Super slots, maybe in conjunction with a few dedis, depending upon your budget and needs.

How much do i need resources?

First we need to determine your target of data seeded (X) in allotted time (Y).

If X=5Tb and Y=1 week:

The formula goes: X in Megabytes / Y in seconds == Bandwidth required

5 242 880 / 604 800 == 8.7Megabytes per second.

In this instance, you will do fine with just a single 2012 slot, and might get away with a single 100Mbps.

X=100Tb, Y=1 week: 104 857 600 / 604 800 == 173.4 Megabytes per second, or roughly 2Gbps.

Since on shared slots we should account for 20% bandwidth max on 1Gbps, and on 100Mbps about 50% for longer term averages, we get: 200Mbps per 1Gbps slot: 25 MB/s 50Mbps per 100Mbps slot: 6.2 MB/s Dedicated servers in practice are about 25-40% bandwidth max on 1Gbps, albeit you might be able to achieve 90% for a few days, and on 100Mbps about 90%.

We choose 2x 1Gbps for getting things started, for a combined: 50 MB/s and remainder as 100Mbps slots: 123.4 / 6.2 = 20 slots for a total of: 124 MB/s Combined: 174 MB/s