Postby janderso » Tue Jun 17, 2008 5:31 am
Hi guys, and Waldorf, thanks for the email and invitation to post. I have been working on the torrent stuff at imageshack.
We have been using Transmission 1.10 CLI via the torrentflux-b4rt package and Python + BitTornado for selective downloading. At the time we were unable to use transmissioncli exclusively as transmissioncli did not seem to have an option to support selective downloading, and the daemonized version just wasn't working for us / refused to move data for some reason (this was a few months ago now though, have not tested lately).
The Python + BitTornado combination requires amounts of memory several times greater then transmissioncli, so we use this client during selective downloads only.
Benefiting from transmissioncli's small memory footprint, using both clients made it possible to handle significantly more simultaneous downloads while keeping selective functionality when needed.
As for the seeding, we are currently seeding at a fixed rate during the download, and stop the process once it finishes. This translates into the logic of "the less healthy a torrent is, the more it gets seeded". Though not realized by many (and I have seen lots of passionate emails come through on this subject), the unhealthy torrents actually reap the most benefit from this. We see very large contribution ratios to (900%+ sometimes) to the sickly torrents over long spans of time.
We also have a special account setup where we permanently seed some linux and freebsd torrents.
The service is still in beta though and things are still being tweaked. I was given the OK to seed to 100% or even 150% which should be implemented before the end of this week.
Also, looking at the recent happenings of transmission's development, the daemonzed beta version is looking absolutely amazing!
Josh
