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