Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Researchers Create Selfish BitTorrent Client

Posted by CmdrTaco on Wed Jan 03, 2007 10:43 AM
from the surprised-it-took-this-long dept.
An anonymous reader writes "Researchers from the computer science department at the University of Washington have released BitTyrant, a new BitTorrent client that is designed to improve download performance via strategic selection of peers and upload rates. Their results call into question the effectiveness of BitTorrent's tit-for-tat reciprocation strategy which was designed to discourage selfish users. Clients are available for Windows, OS X, and Linux."
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by discord5 (798235) on Wednesday January 03 2007, @10:46AM (#17444832)

    internet bandwidth usage has just gone up by 300% at the University of Washington... Scientists are baffled and blame global warming.

  • Not really selfish (Score:5, Informative)

    by m50d (797211) on Wednesday January 03 2007, @10:48AM (#17444862) Homepage Journal
    It looks like all it's doing is trying to allocate its uploads more efficiently. Which, assuming it works, should improve things overall, and (if it works) may even get adopted into the official protocol.
    • Re: (Score:3, Interesting)

      But it prioritizes users with high upload/download speeds. It's better the way it's now - everybody gets their files. Maybe later but it's equal. At least people seed for longer.

      If you're after communities and sharing current model is better. If you're after fast download but shorter torrent lives - go for new one.
      • Re: (Score:3, Interesting)

        If you're after communities and sharing current model is better. If you're after fast download but shorter torrent lives - go for new one.

        If you're after communities and sharing then you're already part of a private tracker, which keeps a tab on your ratio no matter what client you use. Public trackers are a free-for-all grab. I often grab torrents when the seeds are many and peers few, and don't feel bad about that at all.
      • Ratio sites would probably not ban the client - people will use it just to get the file faster and seed longer (face it - the only way to keep a good ratio is to get in early). Non-ratio'd site will probably ban it because they'd just leech and run.

        Wish that ratio'd sites would take thafact into account - the older the torrent, the less likely it'll be downloaded by new people and the harder it is for seed to keep their ratio. Not everyone can bittorrent at work and refresh every 5 minutes...
      • The biggest bottleneck for people getting files off bittorrent isn't their download speed, but the overall upload speed. Even with fairly large swarms, the overall speed can be pretty bad, since most people get crap for upload, so it kinda makes sense for the person who is uploading at the highest rate to get the file first, so they can then upload at their higher rate to everyone in the swarm.
        Now what would be interesting would be if they client would give priority to those with more upload up to a certa
      • by hal2814 (725639) on Wednesday January 03 2007, @11:21AM (#17445366)
        "But it prioritizes users with high upload/download speeds. It's better the way it's now - everybody gets their files."

        I disagree to an extent. What is high upload/download speed to one node is not neccessarily high upload/download speed to another node. It just depends on the network topography. It's possible for a DSL-connected node to have a faster upload/download connection to a node on a dial-up line than a T3 if the dial-up connection is significantly closer from a network standpoint. If done properly, prioritizing based on uploads could lead to more regionalized torrent relationships. Such a setup still has its downsides but I'm not convinced it's worse or even unfair.
    • Well, it targets uploads at those worth bribing. So those with loads of bandwidth get complete copies faster.

      It all depends on how much impact it has that those who don't seed leave the swarm earlier, since they finish faster. Likely no real damage to the network though.
  • I'd rather see some development towards somehow preventing a client from finishing a download until his Down/Up ratio is at least 0.75. This would be difficult to do since you can't trust the client.
    • Re:leechers (Score:4, Insightful)

      by PingSpike (947548) on Wednesday January 03 2007, @11:21AM (#17445370)
      And when there's 12 seeders and no one besides you downloading...then what? Its rare, but that does happen.
      • Re:leechers (Score:5, Interesting)

        by Nasarius (593729) on Wednesday January 03 2007, @11:39AM (#17445700)
        Not rare, it's extremely common on private sites with specialized material [dimeadozen.org]. I've had trouble raising my ratio above 0.85 on DIME, in spite of having 250KB/s upload. It's annoying, but there's not much you can do about it.
        • Re:leechers (Score:4, Interesting)

          by smellsofbikes (890263) on Wednesday January 03 2007, @12:12PM (#17446250) Journal
          Ditto that. I only torrent stuff that is completely unavailable commercially: so-called "out-of-print" material. (What the hell: it's a bunch of zeros and ones, just like all the other zeros and ones. How can it be out of print?) If you're trying to get soundtracks from obscure 1980's movies or ripped '50's jazz LP's, it's pretty frequent that the number of seeders vastly outnumbers the number of people who are still trying to find it.
  • However it will be only a matter of a couple days before people/trackers just start banning the client. (even thoguh it soundsl ike it is not actualy a bad client).

    The only possible downside of the client is that people who regularly hit and run will be doign so that much faster (and thus end with an even lower ratio).

    so, a nifty tool in the hands of the godly, and an abomination in the hands of sinners. (or somethign to that effect)
  • The private trackers, which require login and facilitate banning of users who abuse the system, will simply deal with this as they always have. That's always been one of the protocol's inherent defenses against something like this.
    • by simm1701 (835424) on Wednesday January 03 2007, @11:16AM (#17445274)
      Actually this client would likely be favoured by the private tracker sites.

      The private tracker already gives you plenty of incentive to make sure your ratio is >1 - even asside from basic morals.

      The design of this client means those with higher speed uploads available will complete sooner, and thus you will end up with more high speed seeders.

      Seeders who since they are members of private trackers are probably going to stick around until ratio >1

      True I admit on piblic trackers something like this may not be as helpful or beneficial, but you can't have everything.
  • Not necessarily good (Score:5, Interesting)

    by grimsweep (578372) on Wednesday January 03 2007, @10:58AM (#17444996)
    Selfish selection of peers can lead to cliques of clients on the same network. Tit-for-tat has been proven as a highly effective strategy in games resembling the iterated prisoner's dilemna, but it can be defeated when a large enough group of of agents cooperate. This link [discourse.net] has more.
  • Not so selfish. (Score:5, Insightful)

    by ckdake (577698) <ckdake@ckTOKYOdake.com minus city> on Wednesday January 03 2007, @11:00AM (#17445042) Homepage
    RTFA. They didn't create a client that is "selfish" by trying to avoid uploading. They created a client that is selfish by first allocating more upload capacity to other clients that will send them more when they upload more, and only allocate the remaining upload capacity to clients where benefits from increased uploading are not certain. If you read their paper, they regularly bring up the effects of this on the entire network and they don't know if it's good, bad, or has any effect on the network (and not for a lack of trying)
  • I'm surprised it took this long. Or is it just that we're only hearing about it now, but such clients have existed for ages?

    By the way, am I right in thinking good behavior can never be enforced in peer to peer systems?
  • by meese (9260) on Wednesday January 03 2007, @11:04AM (#17445092)
    Some folks at ETH Zurich took it one step further, and wrote a client - BitThief [dcg.ethz.ch] - that doesn't upload and yet still can download as fast as a regular client. This is especially valuable in countries that define copyright violation to be the uploading of content.
  • by evilviper (135110) on Wednesday January 03 2007, @11:19AM (#17445324) Journal
    The anti-leech technology of the bittorrent protocol remains effective. Those ranting about this just haven't bothered to read... This client (despite the unfortunate name) is just smarter about how to use upload bandwidth, in an async world.

    In fact, I would say this is an IMPROVEMENT in some ways over bittorrent's default behavior, as it will dedicate more of your outgoing bandwidth to higher-speed peers. They, presumably, can then serve up more data to others than a low-speed peer reasonably could.

    Instead of being the end of bittorrent, this could really improve the health of the P2P network, increasing speeds and decreasing download times for everyone (not only those using this program).
      • by evilviper (135110) on Wednesday January 03 2007, @04:35PM (#17450608) Journal
        It seems like this is just a scheme to make the rich richer and the poor poorer.

        That's far too simple a way to look at it. The analogy just doesn't hold up.

        It's giving less of an advantage to those with slow upload speeds (leeches), and high download speeds, but those with low speeds stand to benefit nearly as much as those with high-speed connections. It will take less time to have more full copies of a torrent shared, on higher speed hosts, with lots of bandwidth to spare.

        The only senario in which the low-speed clients lose out, is at the very beginning, when only one peer has a full copy, and the high-speeds are actively sharing among each other and competing for access. After that inital rush, the low speed connections should have full-speed access, and more peers with full copies to chose from. The only way that wouldn't work is if ALL the high speed connections disconnect instantly afterwards.

        It really should make bittorrent better all-around. The potential for abuse is only marginally higher. And the low-speed (leeches) only lose a little bit in certain senarios, but stand to gain even more in the end, bring them past the break-even point as well.
  • by stewbacca (1033764) on Wednesday January 03 2007, @11:45AM (#17445790)
    I'd love to give it a spin, but at 2kbs download for the client installer I'll be here all night. Maybe I can find a torrent for it for a faster download...oh the irony.
  • Trying it out now (Score:4, Informative)

    by Culturejammer (541174) <Raven_powers@nosPaM.freeze.com> on Wednesday January 03 2007, @12:57PM (#17446964)
    Gotta say, these speeds are really impressive. Azureus 2.5 would download at about 35kb/s, while the same torrent on BitTyrant is 400kb/s. I use a private torrent network, so I'll have to make up for the ratio afterwards; but still, it's great to get things so quickly.
  • by Deathlizard (115856) on Wednesday January 03 2007, @01:46PM (#17447776) Homepage Journal
    Emule has a system like this, and it basically slows everything down in the name of fair sharing. It takes absolutely forever to start downloads, since you're stuck in a vicious "chicken and egg" circle of "I can't upload anything to download" and "I can't download anything to upload".

    As it stands, Bittorrent is how the Edonkey protocol used to be before ratio systems were added to the clients; Fast. After Edonkey started adding anti-leech systems to the clients, the speed went into the toilet, and the queues started skyrocketing.

    I suspect that if this catches on, you can kiss 300kb's downloads goodbye.
    • by lisaparratt (752068) on Wednesday January 03 2007, @10:50AM (#17444906)
      If you bothered to RTFA, you'd realise selfish!=bad.
      • by jdray (645332) on Wednesday January 03 2007, @10:54AM (#17444964) Homepage Journal
        I didn't even have to RTFA to figure that out (yay me, right?). AFAIK, most people who could (would) dediate a serious amount of bandwidth to downloading content quickly would be likely to dedicate a serious slice to uploading, therefore enriching the available bandwith for everyone.
        • Re: (Score:3, Informative)

          I dunno. Seems to me that with ADSL and particularly cable connections here in the UK, downstream bandwidth has gone up and up while upstream hasn't changed so much. For instance, one provider offers 10Mb/s downstream, but only 512k upstream.
      • by Holmwood (899130) on Wednesday January 03 2007, @12:49PM (#17446818)
        From the 'article' (really just a brief overview), it's clear that it will generally at present improve performance for the BitTyrant user; it will also statistically improve performance for any peer with substantial spare upload capacity, regardless of client used.

        This paper http://www.cs.washington.edu/homes/piatek/papers/B itTyrant.pdf [washington.edu] [cs.washington.edu] goes into considerably more detail, and is well worth reading if you have a nodding acquaintance with the BT protocol and elementary game theory.

        It probably will initially hurt performance for users with saturated upload capacity who cannot contribute any more to the swarm than they are at present.

        It's not at all clear that this is a bad thing, even if everyone switched to BTyrant. A lot could come down to the social behavior of Tyrant users once they become seeders, for example. If a Tyrant keeps a torrent active as long as s/he presently does, it would clearly be an improvement. For those who say "well a tyrant user may not even seed to 1.0"; fine; that Tyrant user won't really benefit much from the protocol.

        Holmwood
    • by jackharrer (972403) on Wednesday January 03 2007, @10:50AM (#17444910)
      Yes, problem is it's similar to changing UserAgent tag in IE or FireFox. Too easy. It's not very viable solution.
    • Re: (Score:3, Insightful)

      Hi, I'm Bill Gates, and I'm going to give you ONE MILLION DOLLARS if you send your credit card info to me.

      See the problem?

    • Re: (Score:3, Informative)

      AFAIK, all bittorrent clients have a "UserAgent"-kind of field. If that happens to be BitTyrant, ban the user.

      If it's anything like a browsers UserAgent field, I have a set of WWW::Mechanize perl scripts pretending to be firefox 2.0 on windows.

    • Re: (Score:2, Informative)

      by Anonymous Coward
      read the article, it will actually help uploads be more efficient.
    • by tdc_vga (787793) on Wednesday January 03 2007, @10:55AM (#17444974)
      No offense, but that can be spoofed quite easily. Make it say BitTorrent, uTorrent, or Azureus and then what? As the co-founder of Azureus this has always been a problem and threat to the BT protocol. The best clients can do is make sure packets are being spread once they're sent to another person. The algorithm works like this --send a "rare" packet, watch to make sure another client shows up with that rare packet in X time. Clients should send their rarest packets first, to keep the swarm happy. So if the packet doesn't show up, you've got a leech and your drop him in the Queue. TdC
      • Re: (Score:3, Interesting)

        > Clients should send their rarest packets first, to keep the swarm happy.
        > So if the packet doesn't show up, you've got a leech and your drop him in the Queue.

        This technique can easily be circumvented. A leech client can co-operate with another leech client. As soon as he receives your rare packet, he can tell the other client to pretend to have it, too (without actually sending it).

        It makes sense when he does the same for the other client, so both can leech from the swarm.

        The only difficulty is ho
      • Re: (Score:3, Interesting)

        I have a question: Why the hell is bittorrent so slow? I have a 8MB connection and it downloads slower than I used to get on 56k over non-bittorrent.

        Rather than worrying about leeches, why not concentrate on speed?
        • by swillden (191260) * <shawn-ds@willden.org> on Wednesday January 03 2007, @03:05PM (#17449118) Homepage Journal

          I have a question: Why the hell is bittorrent so slow? I have a 8MB connection and it downloads slower than I used to get on 56k over non-bittorrent.

          Most likely it's misconfiguration on your part. Specifically, you're behind router doing network address translation or a firewall that is blocking inbound connections on the key ports.

          In order for you to get good download performance you have to upload at a reasonable rate (at least with clients other than BitTyrant). To do that, you have to make it possible for other peers to connect to your machine.

          Odds are it's a NAT problem. See if you can configure your router to forward incoming TCP and UDP packets on ports 6881-6889 to your computer. Even easier, if your router supports Universal Plug-n-Play (UPNP), get a client that does (like Azureus) and tell it to use UPNP. That will allow the client to automatically tell the router how to configure itself.

          Once you get the network configuration right, you also need to make sure your upstream connections are choking your downloads, as can happen with braindead ISPs (i.e. pretty much all phone and cable companies). Use your client's upload rate configuration parameter and set it to a little less than the upstream rate that your connection provides. I have 384kbps upload rate and I find I can send as much as 35KBps without trouble.

          I have a 5Mbps connection, and I routinely get 500KBps on popular torrents.

          • Re: (Score:3, Informative)

            "as can happen with braindead ISP"

            It can happen on any ISP. This is a limitation of TCPIP and the upload buffers in all the devices on the network behind your worst bottleneck.

            When TCP decides it can send more data, it dumps a whole window size load of packets onto the network. These will clog up your modem / router's transmit buffers. Normally not a huge drain, but if you're uploading to a number of hosts this can add significant lag for the small ACK packets you have to send periodically. If you can't s

    • by nweaver (113078) on Wednesday January 03 2007, @11:21AM (#17445362) Homepage
      BitTyrant (read the paper) [i]follows the protocol[/i].

      From any other peer, you can't tell whether someone is using the BitTyrant bandwidth selection strategy or the default allocatino strategy, and user agent is, of course, meaningless.
      • Re: (Score:3, Informative)

        RTFA

        That is exactly what the client does

        basucly it alocated upload so that it will likely improve performance, if it can not come up with a spot that will improve performance then it will dump that alocation on other users.

        The only downside is that peopel who would hit and run can do so faster.
    • Re:Trivial result (Score:5, Insightful)

      by simm1701 (835424) on Wednesday January 03 2007, @11:11AM (#17445188)
      Did you actually read the paper?

      They are looking at improving download time for that user and the overall swarm by the use of their algorithm.

      The idea being that you share all the upload space you have - but you do it in such a way as to maximise what you can download in the same amount of time.

      This in turn means that when you have finished downloading the file the number of copies within the swarm will have increased - also those that shared with you more will have been able to download quicker themselves.

      A client like this will penalise selfish or greedy uploaders far more than the normal client as it rewards those that give back.

      Give a leach a block and he will have downloaded that block, teach a leach to seed and he shall have blocks for the rest of his life.
    • Responsible researchers would actually RTFA...

      Something tells me that this guy is looking for karma instead of doing good research.
    • Ummm... it doesn't? (Score:5, Informative)

      by Xenographic (557057) on Wednesday January 03 2007, @11:21AM (#17445358) Homepage Journal
      It doesn't trust the client. It's just greedier about allocating "spare" bandwidth--that is, bandwidth the other clients can't pay you back for. From their FAQ:

      Q: How is BitTyrant different from existing BitTorrent clients?

      BitTorrent differs from existing clients in its selection of which peers to unchoke and send rates to unchoked peers. Suppose your upload capacity is 50 KBps. If you've unchoked 5 peers, existing clients will send each peer 10 KBps, independent of the rate each is sending to you. In contrast, BitTyrant will rank all peers by their receive / sent ratios, preferentially unchoking those peers with high ratios. For example, a peer sending data to you at 20 KBps and receiving data from you at 10 KBps will have a ratio of 2, and would be unchoked before unchoking someone uploading at 10 KBps (ratio 1). Further, BitTyrant dynamically adjusts its send rate, giving more data to peers that can and do upload quickly and reducing send rates to others.
    • Re: (Score:3, Interesting)

      Hi,

      Indeed, it's true that BitTyrant will not always improve performance, even when directly compared to other clients on the same torrent at the same time! There are several reasons for this:
      • Data availability: Suppose seeders are sending out data at 20 k/sec, and a complete copy does not yet exist in the swarm. Then, even if you start downloading quickly, eventually you will catch up to the data production point and download at no faster than 20 k/sec.
      • Luck of the draw: sometimes, you'll get a lucky p