1 / 22

Supercharging PlanetLab : a high performance, Multi-Application, Overlay Network Platform

This article discusses the concept of supercharging PlanetLab, a group of computers over the Internet used as a testbed for research. It explores the limitations of PlanetLab and proposes a solution to enhance its performance by introducing supercharged nodes. The architecture of a supercharged node is explained, highlighting the use of network processors. Evaluation results and future work are also discussed.

kellid
Télécharger la présentation

Supercharging PlanetLab : a high performance, Multi-Application, Overlay Network Platform

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. Supercharging PlanetLab : a high performance, Multi-Application, Overlay Network Platform Written by Jon Turner and 11 fellows. Presented by Benjamin Chervet 8 April 2009

  2. Content : • Context • Motivation • How to supercharge PlanetLab ? • Evaluation • Summary

  3. Context : Overlay Network ? • Computer Network built on Top of another • Examples • P2P Network over the Internet • Dial Up Internet over Telephone Network • PlanetLab over the Internet

  4. Context : PlanetLab • Group of computers over the Internet • Used as a testbed for research and deployment • Shared overlay infrastructures.

  5. Motivations : PlanetLab limitations • Applications run as user-space processes in virtual machines. • Limited throughput • High, unpredictable latency • => What is the solution ?

  6. Supercharging: How works a node right now ?

  7. Objectives of a supercharge nodes • Better IO and processing performances • Not too hard for users to take advantage of the modifications. • Current PlanetLab should run on the new nodes.

  8. Supercharged node

  9. Architecture of a supercharged node Server blade supporting standard PlanetLab environment. Conventional server, coordinates system components and synchronizes with PlanetLab Network processor supporting applications fast-paths Forward the packets to correct PlanetLab environments Blade containing data switch and control switch.

  10. What is a Network processor ? • Use of Network processor technology • A kind of processor specially designed to handle network operations. • Programmable • Typically used in Routers, switchs and firewalls.

  11. Architecture of a NP devices • 16 Multi threaded (Mes) • Fast nearest neighbor connections for pipelined apps. • 3 SDRAM and 4 SRAM channels • Management Processor for control

  12. NP devices • How a NP takes advantages from multi threading ? • Cope with the memory latency gap. • Round robin

  13. System Control Divided in two paths: Pink : Normal Path Blue : Fast Path

  14. Using the fast path • Process 8 packets concurrently. • Fast path shared by slices more efficiently than the old fashion nodes.

  15. GPE improvements • Use better performance hardware • Change the scheduling of applications to improve the latency. • Number of token reduced.

  16. Evaluation of the improvements • Implementation of real world applications. • IPv4 arrive/depart in UDP tunnels. • Internet Indirection Infrastructure (i3)

  17. I3 • Packets contain triggers matched to IP addresses • No match at local node results in Chord forwarding

  18. IPv4 Throughput Comparison

  19. IPv4 Latency Comparison

  20. I3 Latency Comparaison

  21. IPv4/i3 Fast Path throughput comparison

  22. Summary • Supercharged nodes remove the limitations of PlanetLab Nodes • Easy to deploy and adapt to existing structures. • Future work: • Automatic NPE code verification • Flexible NPE implementations

More Related