1 / 10

Image Application Redux

This document outlines a robust architecture for streaming video using Redux, focusing on Quality of Service (QoS) management. The receiver subscribes to a video stream and must maintain a balanced load from the video server, avoiding both starvation and flooding. Key components include distributed QoS code, TCP communication for connection management, and sender-receiver feedback channels. The sender application pulls images, and the receiver processes them, ensuring adherence to Service Level Agreements (SLA) while monitoring CPU usage and managing timing effectively.

juro
Télécharger la présentation

Image Application Redux

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. Image Application Redux • Still: receiver subscribes to stream from video source • And: Receiver must not be swamped or starved by video server • Things to note: • Code for QoS gets distributed • QoS code interleaved

  2. Base Code Just TCP communication Binding, connecting, marshalling, etc. No application code No QoS

  3. Sender Control • Sender-side Feedback channel • MUXs control messages • Binds, connects • TCP transport

  4. Sender SLA Implements SLA pieces for sender Param’ed by the SLA Can send messages over the control channel Responds to receiver feedback

  5. Sender Application • Pulls image from source • Uses Infopipe to send image

  6. Receiver Control • Receiver-side feedback channel • DeMUXs control messages • Binds, connects • TCP transport • Mirrors sender’s control code

  7. Timing Code • Inserts variables for time • Inserts system timing calls

  8. CPU Monitor • Calls system for resource usage • Uses timing from timing aspect • Calculates CPU use %

  9. Receiver SLA • Implements Receiver end of SLA • Returns feedback via control channel • Acts based on CPU % usage data

  10. Receiver Application • Processes images received off network by Infopipe

More Related