Originally Posted by scubasteve2365
This is normal. I can't send out 46gigs to everyone. The torrent system works because I send data to one person and he sends that same chunk of data to 15 other people and so on.
More like you send out the data in chunks to various people, and then they send the chunks out to the others in the torrent cloud, and they send it out, and so on, and so on, and so on.
But BlackHawk, yes, it's normal that you don't get much from the original seeder, when they are few... you shouldn't. If the original seeder was busy trying to send the same bits to everyone who joined in, it would never get done. The strength of the torrent system is that downloads are distributed by EVERYONE, as fast as possible. The way torrents work, they break a big file up into little pieces. Everyone downloads the pieces, and the software reassembles them into one file again on your end. Meanwhile, you can download the pieces from ANYONE in the torrent, rather than everyone waiting in line for Steve's upload to the first guy to finish. So everyone shares with everyone else, and no single person's bandwidth limit can clog up the entire chain.
The exception, is what we're looking at now: The initial seed. It takes days for anyone with a normal DSL-style upload speed limit (much lower than the downloading speed limit) to push out 46gb of materials. No matter who he pushes it to (hopefully only one person... if he pushed 46gb to even two people, it would take twice as long to finish the initial upload!), it's going to take a fixed amount of time. The software usually jumps around, distributing pieces to various people in connected in the torrent's cloud, so they can turn around and send them to others, without overwhelming any one person too badly.
As Steve pushes one chunk to someone, that person now has that piece also. And now they can upload it to someone else (without slowing Steve down any further). Then there are three
people with that initial chunk, (while Steve continues to push pieces out to that first person or others, in the background). So if you join in right then, there are three
people pushing out those early pieces all at once, so your
download speed of those initial pieces ends up as an aggregate of all the other people's speed (possible three times Steve's original upload speed, at that point). Once you get 30, or 100, or 500+ people all sharing the same bits of the file, your download speeds can get insanely fast.
BUT, eventually, in these early phases, you catch up, and you have already downloaded everything that's Steve has thus far managed to upload, with his single DSL line. That's the slow situation we're currently in. If he can get the files to someone else via personal delivery/fedex/whatever of a drive, they can join in as fully-participating seeds as well, which would cut the initial seeding time in half, but I guess that didn't work out as hoped due to a problem with the initial file.
In a week (less, more likely), once Steve manages to push out the full file, a whole bunch of people will be seeding the file all at once. So your download speed will be silly fast... likely, as fast as your line is actually capable of working, literally pegged at the limit. But not until enough people have the whole file, which brings us back to the initial seed's upload speed limit.
Going back to your initial question, it absolutely makes sense that only a small part of your files will have come from the initial seeders... because everyone else connected is sharing. If there are 100 people in the collective, and only one of them is seeding, your odds are 1 in 100 that any particular piece will have come directly from the original seeder, as opposed to someone else.
I've simplified a bit, but hopefully this is at least somewhat clear, so people understand why it's slow at the moment, and how it will speed up soon enough.
More here: https://secure.wikimedia.org/wikiped...%28protocol%29