1 / 9

Producer and Consumer Problem - An QoS Guaranteed Queuing System with an Adaptive Server Design

Producer and Consumer Problem - An QoS Guaranteed Queuing System with an Adaptive Server Design. 2007/05/23. Producer / Consumer Problem. Bounded Buffer: message queue size 30 Producer (Client) Randomly produce 1 to 10 producers with randomly selected period from 100 to 500 ticks.

terrel
Télécharger la présentation

Producer and Consumer Problem - An QoS Guaranteed Queuing System with an Adaptive Server Design

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. Producer and Consumer Problem- An QoS Guaranteed Queuing System with an Adaptive Server Design 2007/05/23

  2. Producer / Consumer Problem • Bounded Buffer: message queue size 30 • Producer (Client) • Randomly produce 1 to 10 producers with randomly selected period from 100 to 500 ticks. • On each arrival, the producer puts one-character message to the message queue. • Consumer (Server) • A consumer consumes the message queue in a FIFO manner.

  3. QoS Guarantees • A master task is created to collect information and inform server (through mailbox or MsgQ) so that the server could adjust its service rate • to prevent buffer overflow and underflow • to keep the service rate • as low as possible • as stable as possible

  4. Hierarchical Framework Master task 2 Get the execution information and buffer status 3 Adjust the delay time Statistic task 1 1 Producer Consumer

  5. Output Requirements (1/2)

  6. Output Requirements (2/2) • Inter-arrival time • The arrival time of the latest arrival • Underflow rate • Overflow rate

  7. What do You Turn in? • Your files SHOULD include: • Source code file (test.c) and associated files (compressed in a file, such as b92123456.zip) • Report • You should explain: • Your code • Problems encountered and solutions • As detailed as possible • At most 4 pages

  8. Deadline • DeadlineS • 3 weeks later (23:59, June 13) • Submit the compression files to TA • johnson@newslab.csie.ntu.edu.tw • Email title: [rts2007 project submission] your_student_id • Demo • 5 people randomly selected

  9. Bonus • 10%: You can propose a mechanism to achieve the QoS guarantees in the real-time fashion and reduce the number of reconfiguration.

More Related