1 / 9

Project Proposal

Project Proposal. “Profile-driven QoS-aware Online Services” by Amitayu Das Sri Hari Krishna Narayanan CSE 598B Fall 2005. Problem in QoS satisfaction. Demand  resource requirement allocated resource Application characteristics Time-varying demand, transient overload

ludlow
Download Presentation

Project Proposal

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. Project Proposal “Profile-driven QoS-aware Online Services” by Amitayu Das Sri Hari Krishna Narayanan CSE 598B Fall 2005

  2. Problem in QoS satisfaction • Demand  resource requirement allocated resource • Application characteristics • Time-varying demand, transient overload • Limited resource • Dynamic system management policies/mechanisms

  3. Resource-profiling • How resource is being used by application(s): act of capturing that data • What sort of data? (workload, appln, system, architecture parameters etc.) • Collect data at regular intervals • Mapping: (λwl, δwl) ==f==> (θcpu, θmem, θdisk)

  4. How does it help? • Profiling helps in understanding application characteristics • Helps in better resource allocation, better control • Helps in prediction of performance • How to decide optimal interval-length? • How to decide optimal interval-length online?

  5. Objective • Evolve to decide about the optimal interval-length in a self-tuning manner • Different time-points may have different optimal interval-length: figuring that out • Allocate resource based on new profiles to satisfy QoS: self-tuning performance management

  6. Strategies • Offline determination: • Try to capture “significant change” • Get profiles with different interval-length • Define metric to compute utility of a profile • Decide the best interval-length from best profile • Online determination: • Figure out if overload of offline method is tolerable or not • If not, then come up with other mechanism • Resource Allocation: not yet decided

  7. Plan (time-frame) • Literature survey: throughout • Offline measurement: • Set up system (kernel instrumentation): 2 weeks • Data collection: 3 weeks • Analysis: 2 weeks • Online measurement: • Check for the overload: 2 weeks • Formulating other strategies: undetermined • Resource allocation: depends on above

  8. References • “Performance Modeling and System Management for Multi-component Online Services” by C. Stewart et al. • “An Automated Profiling subsystem for Qos-aware Services” by T. Abdelzaher • “Load Profiling in Distributed Real-time Systems” by A. Bestavros • “Measuring and Characterizing System Behavior Using Kernel-Level Event Logging” by K. Yaghmour et al. • “Resource Overbooking and Application Profiling in Shared Hosting Platforms” by B. Urgaonkar et al.

  9. Questions ??? • Thank You !!!

More Related