1 / 13

Reducing Server and Network Load with Shared Buffering

This paper presents a novel approach to reducing server and network load through shared buffering techniques. Authors Somaya Arianfar, Pasi Sarolahti, and Jörg Ott from Aalto University outline the challenges posed by sudden traffic spikes, lack of Content Delivery Network (CDN) agreements, and application-specific solutions. They introduce a load control architecture that emphasizes application independence, object size independence, and the design of a receiver-based transport protocol. This study aims to optimize network performance by implementing buffered storage sharing among clients, ensuring a more resilient and efficient streaming experience.

nikki
Télécharger la présentation

Reducing Server and Network Load with Shared Buffering

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. Reducing Server and Network Load with Shared Buffering Somaya Arianfar, PasiSarolahti, JörgOtt Aalto University 10.12.2012 CSWS’12, Nice, France

  2. Outline • Background and problem statement • Goals • Design • Byte stream buffering • Store-me bits • Load Control Architecture • Receiver-based Transport Protocol • Summary

  3. Background Client 1 Proxy Server Server Client 2 Bottleneck Client 3 Client 4

  4. Background CDN Client 1 Client 2 Server Client 3 Client 4

  5. Problem Statement • Sudden traffic spikes • Application specific solutions • No CDN agreements => server goes down • E.g. links from Dig and Twitter • Proxy’s violation from end-to-end argument • E.g. Security issues

  6. Main goals • Application independence • Object size independence • Segmentation and network independence

  7. Design: Byte Stream Buffering

  8. Design: Store-me bits and load control Policer Client 1 Buffering node Server

  9. Design: Receiver-based Transport Protocol • Stream label • 20-bytes unique Id • Sequence Number • 64-bits offset • Checksum • Cumulative from the beginning of the stream

  10. Application Interface Client 1 Server

  11. Initial Evaluations

  12. Summary • Storage sharing in the network • Application independent stream buffering • Load controlled architecture • Pull-based transport protocol

  13. Questions? Thanks!

More Related