1. Hrishikesh Amur, Karsten Schwan Georgia Tech

2. Circuit level Circuit level: DVFS, power states, clock gating (ECE) Chip and Package Chip and Package: power multiplexing, spatiotemporal migration (SCS, ECE) Board Board: VirtualPower, scheduling/scaling/operatin g system… (SCS, ME, ECE) Rack Rack: mechanical design, thermal and airflow analysis, VPTokens, OS and management (ME, SCS) Power distribution and delivery (ECE) http://img.all2all.net/main.php?g2_itemId=157 Datacenter and beyond Datacenter and beyond: design, IT management, HVAC control… (ME, SCS, OIT…) focus of our work:

3. Data-intensive applications that use distributed storage

5.  Power off entire nodes

13.  One replica of all data placed on a small set of nodes  Primary replica maintains availability, allowing nodes storing other replicas to be turned off [Sierra, Rabbit]

14. Where is new data to be written when part of the cluster is turned off?

16.  Temporary off-loading to ‘on’ nodes is a solution  Cost of additional copying of lots of data  Usage of network bandwidth  Increased complexity!!

17.  Failure of primary nodes cause a large number of nodes to be started up to restore availability  To solve this, additional groups with secondary, tertiary etc. copies have to be made.  Again, increased complexity!!

19. Provide fine-grained control over what components to turn off

20. Switch between two extreme power modes: max_perf and io_server

21. Fine-grained control allows all disks to be kept on maintaining access to stored data

22. SATA Switch Asterix Node Obelix Node

23. SATA Switch Asterix Node Obelix Node VMM

24. SATA Switch Asterix Node Obelix Node VM

25. SATA Switch Asterix Node Obelix Node VM

26. Increased Performance/Power

32.  Turning entire nodes off complicates DFS  Good to be able to turn components off, or achieve more power-proportional platforms/components  Prototype uses separate machines and shared disks

33.  Static ◦ e.g., DFS, DMS, monitoring/management tasks…  Dynamic ◦ e.g., based on runtime monitoring and management/scheduling… ◦ helpful to do power metering on per process/VM basis  X86+Atom+IB…

34.  Built power profiles for various platform resources ◦ CPU, memory, cache, I/O…  Utilize low-level hardware counters to track resource utilization on per VM basis ◦ xenoprofile, IPMI, Xen tools… ◦ track sets of VMs separately  Maintain low/acceptable overheads while maintaining desired accuracy ◦ limit amount of necessary information, number of monitored events: use instructions retired/s and LLC misses/s only ◦ establish accuracy bounds  Apply monitored information to power model to determine VM power utilization at runtime ◦ in contrast to static purely profile-based approaches