The Latest on The Green Grid s Productivity Research

Transcription

1 The Latest on The Green Grid s Productivity Research Zeydy Ortiz, Ph. D., IBM Metrics & Measurement Work Group Join The Green Grid Technical Forum conversation on Twitter! As you are tweeting, use #TGG11

2 Agenda Data Center energy Productivity (DCeP) Experimental Validation Measuring the Productivity Proxies Evaluating the Proxies 2

3 Ease of Use was ranked as the most important criterion when evaluating the productivity proxies proposed by The Green Grid

4 Productivity Data Center Energy Productivity: DCeP = Useful work produced / Total Data Center energy consumed producing this work Source: The Green Grid White Paper #13 A Framework for Data Center Energy Productivity

5 Productivity Proxies Group 1 DCeP-based Proxies Proxy #1: Useful Work Self-Assessment and Reporting #2: DCeP Subset by Productivity Link #3: DCeP Subset by Sample Load 2 Bits #4: Bits per Kilowatt-hour 3 CPU Utilization #5: Weighted CPU Utilization SPECint_rate #6: Weighted CPU Utilization SPECpower #7: Compute Units per Second (CUPS) 4 OS Instances #8: Operating System Workload Efficiency Source: The Green Grid White Paper #17 Proxy Proposals for Measuring Data Center Productivity and The Green Grid White Paper #24 Productivity Proxy Proposals Feedback Interim Results

6 Experimental Validation Test and measure 8 productivity proxy proposed against the evaluation criteria Use same application and workload to measure data center productivity and correlate to energy use Use a common platform to simultaneously measure the metrics relevant to all proxies Have test run and validated by an independent 3 rd party and publish results 6

7 PNNL Testbed: NW-ICE The Energy Smart Data Center (ESDC) testbed facility is located in the William R. Wiley Environmental Molecular Sciences Laboratory (EMSL), a U.S. Department of Energy national scientific user facility located at Pacific Northwest National Laboratory (PNNL) in Richland, Washington. NW-ICE, the focus of the testbed, is an IBM System Cluster 1350 using SprayCool technology. 192 nodes of x3550 Processors: dual Quad-core Intel Xeon E5345 Clovertown Operating System: Linux SLES 10 Memory: 16 GB (8 x 2GB) Local disks: two 160 GB Networking: Dual integrated Gigabit Ethernet controllers Source: 7

8 Infrastructure Rack 1 Rack 2 Server 1 Server 2 Client 1 Server 11 Server 12 Server 3 Server 4 Server 5 Server 6 Server 7 Server 8 Network Switch Client 2 Client 3 Client 4 Network Switch Server 13 Server 14 Server 15 Server 16 Server 17 Server 18 Server 9 Server 10 Client 5 Server 19 Server 20

9 Application and Workload Application: Enterprise relational database IBM s DB2 has been instrumented with Intel s Energy Checker SDK Energy Checker allows correlation of productivity to energy used and aggregation of data Workload: Transaction processing over XML (TPoX) Simulates transactions in a financial institution (brokerage house)

10 Overview of Experiments 1. Baseline 2. Different loads per server 3. Decreased network traffic 4. Increased network traffic 5. Increase useful transactions 6. Decrease useful transactions 7. Half of the systems active, half of the systems idle 8. Half of the systems active, half of the systems shutdown 10

11 Runs per Experiment Number of concurrent users per system Time For each experiment, perform 20 runs such that the first will only have 10% of the maximum number of concurrent users. Each subsequent run will add another 10% users until the maximum number of concurrent users is reached. The next runs will decrease the number of users by 10%. The last measurement period will be performed with 0 users (all systems idle).

12 Measuring the Proxies For every run, collect the following information Total # transactions for all systems Total # transactions for a subset Transactions logged by Energy Checker Total # of useful transactions for all systems Total # useful transactions for subset Total # of active OS instances Total outbound network traffic Average CPU utilization during steady state CPU frequency during steady state Average system power during steady state Average cluster power during steady state 12

13 Additional Information to Collect For all servers collect the following information Site Survey: Server Make and Model Age CPU type and number installed Memory capacity Disk capacity Determine: SPECint_rate2006 SPECpower_ssj2008 CUPs Document methodology used to measure proxies 13

14 Proxy #1: Useful Work Self-Assessment and Reporting Overview: Instrument all applications to report their productivity ; assign weights by application Metric: Custom productivity metric transactions reported by applications Data Collection: Instrumentation: Transaction/Application level Tools: Application Performance Monitor Collect: Number of transactions Results: Transactions/kWh 14

15 Proxy #2: DCeP subset by Productivity Link Overview: Instrument applications with Energy Checker (formerly Productivity Link) to measure the number of transactions in a time period Metric: Custom productivity metric transactions from applications selected Data Collection: Instrumentation: Transaction/Application level Tools: Intel s Energy Checker Collect: Number of transactions Results: Transactions/kWh 15

16 Proxy #3: DCeP subset by Sample Load Overview: Measure a subset of the systems with Sample Load to estimate the potential productivity of the DC Metric: Transactions from Sample Load Data Collection: Instrumentation: Transaction/Application level Tools: Workload generator Collect: Number of transactions Results: Transactions/kWh 16

17 Proxy #4: Bits per Kilowatt-hour Overview: Measure the outbound network traffic Metric: Network traffic in bits Data Collection: Instrumentation: Network level Tools: Network Monitor Collect: Network outbound traffic in bits Results: Bits/kWh 17

18 Measuring Proxy #4 Results presented at the 3 rd Annual Green Grid Forum 18

19 Proxy #5: Weighted CPU Utilization SPECint_rate Overview: Measure CPU utilization of each server. Use SPECint_rate as the maximum productivity of a server. Determine the SPECint_rate that would have been produced at the corresponding CPU utilization. Metric: SPECint_rate@CPU Frequency * CPU Utilization Data Collection: Input: Processor Frequency Instrumentation: System level Tools: System Performance Monitor Collect: CPU utilization, Processor Frequency Results: SPECint_rate * CPU utilization/kwh 19

20 Measuring Proxy #5 Results presented at the 3 rd Annual Green Grid Forum 20

21 Proxy #6: Weighted CPU Utilization SPECpower_ssj2008 Overview: Measure CPU utilization. Use SPECpower results to determine the number of ssj_ops that would have been produced at the measured CPU utilization. Metric: CPU Utilization Data Collection: Input: SPECpower_ssj2008 Instrumentation: System level Tools: System Performance Monitor Collect: CPU utilization Results: ssj_ops/kwh 21

22 Proxy #7: Compute Units per Second Overview: Measure CPU utilization. Determine the Compute Units that would have been used at the corresponding CPU utilization based on the age of the system. Metric: Compute Units * CPU Utilization Data Collection: Input: Age of server, Compute Units Instrumentation: System level Tools: System Performance Monitor Collect: CPU utilization Results: CUPs/kWh 22

23 Proxy #8: Operating System Workload Efficiency Overview: Count number of OS Images in DC Metric: OS Images Data Collection: Instrumentation: System level Tools: Server management Collect: Number of OS Images Results: OS/kW 23

24 Evaluating the Proxies Source: The Green Grid White Paper #24 Productivity Proxy Proposals Feedback Interim Results 24

25 Most Important Criteria EASE OF USE Easy to use and require as little setup or decision-making as possible The results should be simple and objective; should not require highly skilled technical personnel to interpret COST Leverage existing data collection tools and infrastructure that would typically be found in the data center Setup effort should be less than one man-week in order to begin collecting the metric No additional capital equipment or software licenses should be required. ACCURACY: Must indicate correctly; it must move in the correct direction and in correct proportion when an action is implemented Source: The Green Grid White Paper #17 Proxy Proposals for Measuring Data Center Productivity 25

26 Assessing the Proxies Changes to infrastructure Changes to IT equipment Changes to applications Tools needed Ease of calculating the proxy Additional information needed to calculate proxies Availability of additional information Ease of setting up proxy data collection Reflects Productivity Energy proportionality Effect of proxy data collection 26

27 Goal of Assessment Proxy #1: Useful Work Self-Assessment and Reporting Agree Evaluation Criteria #2: DCeP Subset by Productivity Link X #3: DCeP Subset by Sample Load X #4: Bits per Kilowatt-hour X #5: Weighted CPU Utilization SPECint_rate X #6: Weighted CPU Utilization SPECpower X #7: Compute Units per Second (CUPS) X #8: Operating System Workload Efficiency X After experiments are performed, proxies will be assessed against evaluation criteria X Disagree

28 Next Steps Experiment design: - Develop experiments to test evaluation criteria - Document data collection and storage procedure for each proxy - Create scripts for load generation and data collection Design of entire study signed off Prepare PNNL facility for experiments Perform Experiments Raw data available Data reduction and analysis Proxies Task Force needs your help! 28

29 Thank you!

30 Thank you for attending The Green Grid Technical Forum 2011 Join The Green Grid Technical Forum conversation on Twitter! As you are tweeting, use #TGG11 30