1 | <environment xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" |
---|
2 | xsi:noNamespaceSchemaLocation="../../XSSimResSchema.xsd"> |
---|
3 | |
---|
4 | <resources> |
---|
5 | <description> |
---|
6 | This example aims to show how to introduce energy-related parameters to the simulation environment |
---|
7 | Simulated architecture consist of data center with 4 racks. Each of them contains 64 computing nodes with 2 processors. |
---|
8 | Speed of every processor is equal 2. All computing nodes have 12GB of memory and 4TB storage. |
---|
9 | For the detailed energy characteristics description, see the following comments. |
---|
10 | Task are submitted to the single cluster built on top of the data center. It is under the control of local scheduler |
---|
11 | with FCFS scheduling policy. |
---|
12 | </description> |
---|
13 | |
---|
14 | <computingResource class="DataCenter" name="dataCenter"> |
---|
15 | <computingResource class="Rack" count="4" name="rack"> |
---|
16 | <computingResource class="ComputingNode" count="64"> |
---|
17 | <description>ComputingNodeEnergyEstimationPlugin will be used to customize estimation of energy consumptions to |
---|
18 | specific applications and hardware on computing node level.</description> |
---|
19 | <energyEstimationPlugin> |
---|
20 | <name>ComputingNodeEnergyEstimationPlugin</name> |
---|
21 | </energyEstimationPlugin> |
---|
22 | <profile> |
---|
23 | <!-- Definition of computing node power profile |
---|
24 | According to it, there are two supported power states: ON and OFF |
---|
25 | Computing node in ON state consume 20 watts, while in OFF state 0. |
---|
26 | Transition between ON and OFF state took 30 seconds ant consumes 30 watts, |
---|
27 | while in the opposite energy consumption rate is equal 60 watts over 40 seconds. |
---|
28 | --> |
---|
29 | <powerProfile> |
---|
30 | <powerStates> |
---|
31 | <powerState> |
---|
32 | <name>ON</name> |
---|
33 | <powerUsage unit="watts">20</powerUsage> |
---|
34 | <transition> |
---|
35 | <to>OFF</to> |
---|
36 | <powerUsage unit="watts">30</powerUsage> |
---|
37 | <time unit="seconds">30</time> |
---|
38 | </transition> |
---|
39 | </powerState> |
---|
40 | <powerState> |
---|
41 | <name>OFF</name> |
---|
42 | <powerUsage unit="watts">0</powerUsage> |
---|
43 | <transition> |
---|
44 | <to>ON</to> |
---|
45 | <powerUsage unit="watts">40</powerUsage> |
---|
46 | <time unit="seconds">60</time> |
---|
47 | </transition> |
---|
48 | </powerState> |
---|
49 | </powerStates> |
---|
50 | </powerProfile> |
---|
51 | <!-- Definition of computing node air throughput profile (for instance fan related with the given node) |
---|
52 | Fan can operate in the 4 states, characterized by name, air flow value and power consumption. |
---|
53 | --> |
---|
54 | <airThroughputProfile> |
---|
55 | <airThroughputState> |
---|
56 | <name>mode1</name> |
---|
57 | <value unit="m3/h">105</value> |
---|
58 | <powerUsage unit="watts">10.3</powerUsage> |
---|
59 | </airThroughputState> |
---|
60 | <airThroughputState> |
---|
61 | <name>mode2</name> |
---|
62 | <value unit="m3/h">110</value> |
---|
63 | <powerUsage unit="watts">10.9</powerUsage> |
---|
64 | </airThroughputState> |
---|
65 | <airThroughputState> |
---|
66 | <name>mode3</name> |
---|
67 | <value unit="m3/h">115</value> |
---|
68 | <powerUsage unit="watts">11.4</powerUsage> |
---|
69 | </airThroughputState> |
---|
70 | <airThroughputState> |
---|
71 | <name>mode4</name> |
---|
72 | <value unit="m3/h">120</value> |
---|
73 | <powerUsage unit="watts">12.1</powerUsage> |
---|
74 | </airThroughputState> |
---|
75 | </airThroughputProfile> |
---|
76 | </profile> |
---|
77 | <computingResource class="Processor" count="2"> |
---|
78 | <description>CPUEnergyEstimationPlugin will be used to customize estimation of energy consumptions to |
---|
79 | specific applications and hardware on computing node level.</description> |
---|
80 | <energyEstimationPlugin> |
---|
81 | <name>CPUEnergyEstimationPlugin</name> |
---|
82 | </energyEstimationPlugin> |
---|
83 | <profile> |
---|
84 | <!-- Definition of processor power profile |
---|
85 | According to it, processor can operate in two p-states: P0 and P1 |
---|
86 | P0 p-state is characterized by operating frequency - 3000, |
---|
87 | voltage level - 1.3 and power usage - 35. |
---|
88 | Next p-state - P1 has the following values: 2666, 1.1, 30 respectively. |
---|
89 | --> |
---|
90 | <powerProfile> |
---|
91 | <parameter name="pState"> |
---|
92 | <property name="name"> |
---|
93 | <value>P0</value> |
---|
94 | </property> |
---|
95 | <property name="frequency"> |
---|
96 | <value >3000</value> |
---|
97 | </property> |
---|
98 | <property name="voltage"> |
---|
99 | <value>1.3</value> |
---|
100 | </property> |
---|
101 | <property name="powerUsage"> |
---|
102 | <value>35</value> |
---|
103 | </property> |
---|
104 | </parameter> |
---|
105 | <parameter name="pState"> |
---|
106 | <property name="name"> |
---|
107 | <value>P1</value> |
---|
108 | </property> |
---|
109 | <property name="frequency"> |
---|
110 | <value>2666</value> |
---|
111 | </property> |
---|
112 | <property name="voltage"> |
---|
113 | <value>1.1</value> |
---|
114 | </property> |
---|
115 | <property name="powerUsage"> |
---|
116 | <value>30</value> |
---|
117 | </property> |
---|
118 | </parameter> |
---|
119 | </powerProfile> |
---|
120 | </profile> |
---|
121 | </computingResource> |
---|
122 | </computingResource> |
---|
123 | </computingResource> |
---|
124 | </computingResource> |
---|
125 | |
---|
126 | <scheduler class="Cluster" name="cluster"> |
---|
127 | <schedulingPlugin> |
---|
128 | <name>FCFSLocalSchedulingPlugin</name> |
---|
129 | </schedulingPlugin> |
---|
130 | <managedComputingResources include="true"> |
---|
131 | <resourceName>rack_1</resourceName> |
---|
132 | <resourceName>rack_2</resourceName> |
---|
133 | <resourceName>rack_3</resourceName> |
---|
134 | <resourceName>rack_4</resourceName> |
---|
135 | </managedComputingResources> |
---|
136 | </scheduler> |
---|
137 | |
---|
138 | </resources> |
---|
139 | </environment> |
---|