1 / 17

An energy-aware framework for dynamic software management in mobile computing systems

An energy-aware framework for dynamic software management in mobile computing systems. Yunsi Fei, Lin Zhong, and Niraj K. Jha. Presented By Vimarsh Puneet. Introduction. What is DSOM ?

hart
Télécharger la présentation

An energy-aware framework for dynamic software management in mobile computing systems

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. An energy-aware framework for dynamic software management in mobile computing systems Yunsi Fei, Lin Zhong, and Niraj K. Jha Presented By Vimarsh Puneet

  2. Introduction • What is DSOM ? • It is a system that optimizes energy consumption by exploring different QoS levels, among different priority based application. • Alternate technique • Energy-efficient hardware • Software optimization • Dynamic power management (DPM) and dynamic voltage/frequency scaling (DVFS)

  3. Main Idea

  4. Challenges • Modify the applications to expose the software knobes • Provide interface for application and OS to communicate • Management of software by certain policies • Energy estimation module

  5. Design Every application needs to provide Controls the execution, creation and termination of processes Monitors the resources and manages their usage

  6. Algorithms used

  7. Coordinator Design • Metadata and process space information • Runtime library • Higher priority application running and low priority application enters.

  8. Adaptation Block • Different execution sequence for different QoS • One single block with global knobs ( flags ) • Many different adaptation blocks • Yielding application take one of the following actions • Suspended • Aborted • Rolled back

  9. Implementation • Registry • Runtime Library • Provides functionalities required by the application to interact with the coordinator App 1 (Client) App 2 (Client) Coordinator (Server) App 4 (Client) App 3 (Client) New Application

  10. Energy estimation module • Video player (Color, Gray, Mono, Threashold)

  11. Energy estimation module • VoIP application,RAT • Speech Recognizer

  12. Experiment Experimental Setup

  13. Results

  14. Results contd..

  15. Experiment with multiple application High priority application joining low priority application

  16. Experiment with multiple application Low priority application joining high priority application

  17. Conclusion • System that meets the user-specified goals and user’s intention • No changes required in the underlying OS • Easily portable to any OS

More Related