1 / 32

A Case Study on How Economic Frameworks Can Bail Out Systems Research

A Case Study on How Economic Frameworks Can Bail Out Systems Research. Emin Gün Sirer Ryan Peterson, Bernard Wong Department of Computer Science, Cornell University United Networks, LLC September 3, 2009. Problem Domain.

seanna
Download Presentation

A Case Study on How Economic Frameworks Can Bail Out Systems Research

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. A Case Study on How Economic Frameworks Can Bail Out Systems Research Emin Gün Sirer Ryan Peterson, Bernard Wong Department of Computer Science, Cornell University United Networks, LLC September 3, 2009

  2. Problem Domain What is the most efficient way to disseminate a large set of files to a large set of clients?

  3. Inefficient High cost of ownership Client-Server server clients

  4. Limited information No control or performance guarantees Peer-to-Peer peer

  5. Traditional Systems Research • Complex problems lead to complex protocols with many parameters • Parameters picked based on a combination of gut feeling and experimentation • Systems tailored to specific workloads • Only intellectual honesty keeps researchers from perfect performance on benchmarks! • Novelty by aggregation • Pick k out of n: CDNs, network coordinates, geolocation, network tomography, …

  6. BitTorrent • Robust, resilient protocol • A combination of randomization and heuristics • Two years until characterized as auctions based on received bandwidth • Lots of incremental research! • Every 10-line tweak => 1 paper • Hacks: Share ratios, manual pruning, … • We lack the tools to tackle difficult problems

  7. Antfarm Goals • High performance • Low cost of deployment • Performance guarantees • Administrator control over swarm performance • Accounting • Enables different resource contribution policies

  8. Antfarm Approach • Key insight: view content distribution as an optimization problem • Hybrid architecture • P2P swarming with a logically centralized coordinator • Clean slate protocol

  9. Antfarm System Model seeder coordinator altruist

  10. Strawman Coordinator • One could schedule every data transfer in the system • All packets for all time • Unscalable, impractical! • Antfarm coordinator makes critical decisions based on observed dynamics

  11. Antfarm Coordinator • Models swarm dynamics • Measures and extracts key parameters • Formulates optimization problem • Calculates optimal bandwidth allocation • Enacts allocation decisions • Maximizes aggregate bandwidth • Minimizes average download time

  12. Antfarm Formalization Maximize system-wide aggregate bandwidth subject to a bandwidth constraint

  13. Response Curves slope = 0 slope = 1

  14. 1500 1000 Swarm aggregate bandwidth (KB/s) 500 0 25 50 75 100 0 Seeder bandwidth (KB/s) Response Curves

  15. Swarms exhibit different dynamics based on size, peer resources, network conditions. . . Swarm Dynamics

  16. Antfarm Optimization A σA + σB + σC = B B C σA σB σC

  17. Performance Control • Can provide swarm performance guarantees • Guarantee minimum level of service • Prioritize swarms

  18. Antfarm Allocation A σA′+ σB′+ σC′= B B C σB′ σA′ σC′

  19. Problems • The optimization problem has limitations • Requires knowing total bandwidth constraint • Applies only to full caches under the control of the coordinator • At the wire protocol level, there are many opportunities for malfeasance

  20. Antfarm++ • Use a currency scheme, called karma, to keep track of peers’ resource consumption and contribution • Every exchange costs some karma to the peer receiving a block, brings karma to the peer providing the block and bandwidth

  21. purse purse ledger ledger peer A peer B Wire Protocol • Coordinator mints small, unforgeable tokens • Peers trade each other tokens for blocks • Peers return spent tokens to the coordinator as proof of contribution coordinator

  22. Tokens & Exchange Rates • Every swarm uses a per-swarm currency, every token has source-destinations marked • Token flows reveal the internal network dynamics to the coordinator • The coordinator can provide incentives in the form of exchange rates • Exchange rates encode the differential in the desirability of participating in different swarms => no need to estimate total BW

  23. Benefits of a Virtual Currency • The cost and benefit of a transaction need not be symmetrical • A block always costs 1 token to the buyer • A block can bring γi karma to the seller • Provide an incentive for peers to join and seed swarms in need

  24. Antfarm Performance

  25. Swarm Starvation BitTorrent starves the singleton swarm

  26. BitTorrent: Starves New Swarm self-sufficient new singleton Swarms, ordered largest to smallest

  27. Antfarm: Seeds New Swarm self-sufficient new singleton Swarms, ordered largest to smallest

  28. Conclusions • Hard problems in systems research can benefit immensely from the application of economics • http://flixq.com showcases our current work

  29. Related Work • Content Distribution Networks • Akamai, CoBlitz, CoDeeN, ECHOS, Coral, Slurpie, YouTube, Hulu, GridCast, Tribler, Joost, Huang et al. 2008, ... • P2P Swarming • BitTorrent, BitTyrant, PropShare, BitTornado, BASS, Annapureddy et al. 2007, Guo et al. 2005, ... • Incentives and microcurrencies • Dandelion, BAR Gossip, Samsara, Karma, SHARP, PPay, Kash et al. 2007, ...

  30. Questions?

  31. PlanetLab Deployment

  32. PlanetLab Deployment

More Related