1 / 18

iOverlay : A Lightweight Middleware Infrastructure for Overlay Application Implementations

iOverlay : A Lightweight Middleware Infrastructure for Overlay Application Implementations. Baochun Li, Jiang Guo, Mea Wang The Fifth ACM/IFIP/USENIX International Middleware Conference (Middleware 2004). Presented by Zhinan Zhou. Contents. Introduction. iOverlay Design.

Download Presentation

iOverlay : A Lightweight Middleware Infrastructure for Overlay Application Implementations

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. iOverlay: A Lightweight Middleware Infrastructure for Overlay Application Implementations Baochun Li, Jiang Guo, Mea Wang The Fifth ACM/IFIP/USENIX International Middleware Conference (Middleware 2004) Presented by Zhinan Zhou

  2. Contents Introduction iOverlay Design iOverlay Performance Case Study Related Work

  3. Why iOverlay? Rapid Implementation Reusable Most of the existing work focuses on algorithm and protocol evaluation. They can share a large amount of supporting elements (deployment, debug, monitoring, etc.) Simple iOverlay provides a simple interface and an efficient underlying infrastructure to minimize the programming burden of overlay application developers.

  4. 2 As generic as possible 4 Blackbox design 1 5 Clean interface Design Objectives 1 1 Careful selection of features 3 Simplifying implementation

  5. message switch engine algorithm application iOverlay Architecture

  6. Highlights Simplified interface iOverlay architectural design Virtualized nodes Maximized performance and portability

  7. Message-based Design • message and message switching engine: • 24-byte header • application data and protocol-specific messages • multi-threaded architecture

  8. Message-based Design (cont.) • message process and switch: • select() • Engine::process() vs. Algorithm::process() • Engine::send()

  9. Message-based Design (cont.) • Algorithm as message handler: • send() function • message types • destruction of messages

  10. Message-based Design (cont.) Zero copying of messages Persistent connection Performance Small footprint

  11. Observer

  12. Performance • Raw message switching: • main overhead: context switching • end-to-end throughput and total bandwidth • nodes on a single platform

  13. Correctness

  14. Network Coding

  15. Service Federation • Service overlay network: • control messages: sAware, sFederate

  16. Service Federation (cont.)

  17. 1 2 3 PLUTO: focuses on lower level connectivity Macedon: focuses on algorithm design Service Cloud: focuses on communication support Related Work

  18. Thank You !

More Related