| 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 queueing system |
|---|
| 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 | <energyEstimationPlugin> |
|---|
| 18 | <name>ComputingNodeEnergyEstimationPlugin</name> |
|---|
| 19 | </energyEstimationPlugin> |
|---|
| 20 | <profile> |
|---|
| 21 | <!-- Definition of computing node power profile |
|---|
| 22 | According to it, there are two supported power states: ON and OFF |
|---|
| 23 | Computing node in ON state consume 20 watts, while in OFF state 0. |
|---|
| 24 | Transition between ON and OFF state took 30 seconds ant consumes 30 watts, |
|---|
| 25 | while in the opposite energy consumption rate is equal 60 watts over 40 seconds |
|---|
| 26 | --> |
|---|
| 27 | <powerProfile> |
|---|
| 28 | <powerStates> |
|---|
| 29 | <powerState> |
|---|
| 30 | <name>ON</name> |
|---|
| 31 | <powerUsage unit="watts">20</powerUsage> |
|---|
| 32 | <transition> |
|---|
| 33 | <to>OFF</to> |
|---|
| 34 | <powerUsage unit="watts">30</powerUsage> |
|---|
| 35 | <time unit="seconds">30</time> |
|---|
| 36 | </transition> |
|---|
| 37 | </powerState> |
|---|
| 38 | <powerState> |
|---|
| 39 | <name>OFF</name> |
|---|
| 40 | <powerUsage unit="watts">0</powerUsage> |
|---|
| 41 | <transition> |
|---|
| 42 | <to>ON</to> |
|---|
| 43 | <powerUsage unit="watts">40</powerUsage> |
|---|
| 44 | <time unit="seconds">60</time> |
|---|
| 45 | </transition> |
|---|
| 46 | </powerState> |
|---|
| 47 | </powerStates> |
|---|
| 48 | </powerProfile> |
|---|
| 49 | <!-- Definition of computing node air throughput profile (for instance fan related with the given node) |
|---|
| 50 | Fan can operate in the 4 states, characterized by name, air flow value and power consumption. |
|---|
| 51 | --> |
|---|
| 52 | <airThroughputProfile> |
|---|
| 53 | <airThroughputState> |
|---|
| 54 | <name>mode1</name> |
|---|
| 55 | <value unit="m3/h">105</value> |
|---|
| 56 | <powerUsage unit="watts">10.3</powerUsage> |
|---|
| 57 | </airThroughputState> |
|---|
| 58 | <airThroughputState> |
|---|
| 59 | <name>mode2</name> |
|---|
| 60 | <value unit="m3/h">110</value> |
|---|
| 61 | <powerUsage unit="watts">10.9</powerUsage> |
|---|
| 62 | </airThroughputState> |
|---|
| 63 | <airThroughputState> |
|---|
| 64 | <name>mode3</name> |
|---|
| 65 | <value unit="m3/h">115</value> |
|---|
| 66 | <powerUsage unit="watts">11.4</powerUsage> |
|---|
| 67 | </airThroughputState> |
|---|
| 68 | <airThroughputState> |
|---|
| 69 | <name>mode4</name> |
|---|
| 70 | <value unit="m3/h">120</value> |
|---|
| 71 | <powerUsage unit="watts">12.1</powerUsage> |
|---|
| 72 | </airThroughputState> |
|---|
| 73 | </airThroughputProfile> |
|---|
| 74 | </profile> |
|---|
| 75 | <computingResource class="Processor" count="2"> |
|---|
| 76 | <energyEstimationPlugin> |
|---|
| 77 | <name>CPUEnergyEstimationPlugin</name> |
|---|
| 78 | </energyEstimationPlugin> |
|---|
| 79 | <profile> |
|---|
| 80 | <!-- Definition of processor power profile |
|---|
| 81 | According to it, processor can operate in two p-states: P0 and P1 |
|---|
| 82 | P0 p-state is characterized |
|---|
| 83 | --> |
|---|
| 84 | <powerProfile> |
|---|
| 85 | <parameter name="pState"> |
|---|
| 86 | <property name="name"> |
|---|
| 87 | <value>P0</value> |
|---|
| 88 | </property> |
|---|
| 89 | <property name="frequency"> |
|---|
| 90 | <value >3000</value> |
|---|
| 91 | </property> |
|---|
| 92 | <property name="voltage"> |
|---|
| 93 | <value>1.3</value> |
|---|
| 94 | </property> |
|---|
| 95 | <property name="power"> |
|---|
| 96 | <value>35</value> |
|---|
| 97 | </property> |
|---|
| 98 | </parameter> |
|---|
| 99 | <parameter name="pState"> |
|---|
| 100 | <property name="name"> |
|---|
| 101 | <value>P1</value> |
|---|
| 102 | </property> |
|---|
| 103 | <property name="frequency"> |
|---|
| 104 | <value>2666</value> |
|---|
| 105 | </property> |
|---|
| 106 | <property name="voltage"> |
|---|
| 107 | <value>1.1</value> |
|---|
| 108 | </property> |
|---|
| 109 | <property name="power"> |
|---|
| 110 | <value>30</value> |
|---|
| 111 | </property> |
|---|
| 112 | </parameter> |
|---|
| 113 | </powerProfile> |
|---|
| 114 | </profile> |
|---|
| 115 | </computingResource> |
|---|
| 116 | </computingResource> |
|---|
| 117 | </computingResource> |
|---|
| 118 | </computingResource> |
|---|
| 119 | |
|---|
| 120 | <scheduler class="Cluster" name="cluster"> |
|---|
| 121 | <schedulingPlugin> |
|---|
| 122 | <name>FCFSLocalSchedulingPlugin</name> |
|---|
| 123 | </schedulingPlugin> |
|---|
| 124 | <managedComputingResources include="true"> |
|---|
| 125 | <resourceName>rack_1</resourceName> |
|---|
| 126 | <resourceName>rack_2</resourceName> |
|---|
| 127 | <resourceName>rack_3</resourceName> |
|---|
| 128 | <resourceName>rack_4</resourceName> |
|---|
| 129 | </managedComputingResources> |
|---|
| 130 | </scheduler> |
|---|
| 131 | |
|---|
| 132 | </resources> |
|---|
| 133 | </environment> |
|---|
