1 / 5

Tapestry on PlanetLab

This document discusses our experiences deploying Tapestry, a peer-to-peer routing platform, on PlanetLab across 67 nodes. We detail the dynamics of large-scale routing and location measurements, emphasizing the necessity for uniform network configurations and isolation to manage latency. Our persistent deployment aims to create a robust application platform for practical utilities, incorporating a decentralized chat service and a deterministic file-sharing system. We present snapshots of our measurements, illustrating routing and loading dynamics within a substantial network of 400+ nodes.

shelby
Télécharger la présentation

Tapestry on PlanetLab

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. Tapestry on PlanetLab Deployment Experiences and Applications Ben Zhao, Ling Huang, Anthony Joseph, John Kubiatowicz

  2. Our Experience • Tapestry on PlanetLab • Deployed Java implementation on 67 nodes • Large scale routing and location measurements • 6-7 node instances per physical node • A wish list • Uniformity in network configuration • Isolation (bounded scheduling latencies) • Dynamically updated pair-wise distance map • Transparent file synchronization ravenben@eecs.berkeley.edu

  3. Our Goals • A persistent Tapestry on PlanetLab • Application platform with extensible P2P routing • Persistent on selection of distributed PlanetLab nodes • Global backbone for larger Tapestry • Dynamic integration via introduction service • Incremental upgrades via ordered node restarts • Practical utility services available to PL users • Application / service control via IM (Shuttle) • Quick and dirty file sharing (Interweave) • Distributed file system (OceanStore) ravenben@eecs.berkeley.edu

  4. Snapshot Measurements • Real Tapestry network of 400+ nodes • Measured routing and location RDP under load • Scheduling / contention artificially increases RDP • Routing RDP median: 2.5  1 • Location RDP median: 5  1 ravenben@eecs.berkeley.edu

  5. Infrastructure Services • Simple but useful utility applications • Shuttle: decentralized chat service • Persistent state replicated across network • Decentralized message routing via Tapestry • Graphical UI, w/ AIM-like functionality • command mode can be used as a wall / zephyr – like tool • Interweave: deterministic file sharing • Simple file sharing via object location • Metadata replicas distributed across network • Search (match) on primary fields, pruning via secondary fields • Locates nearby object replicas ravenben@eecs.berkeley.edu

More Related