- Timestamp:
- 07/18/12 18:00:14 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
xssim/trunk/src/test/rewolucja/schemas/example/coolemall/example2.xml
r322 r326 3 3 4 4 <resources> 5 <computingResource class="DataCenter" count="1" id="dataCenter"> 6 <computingResource class="Rack" count="4" id="rack"> 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"> 7 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> 8 75 <computingResource class="Processor" count="2"> 9 76 <energyEstimationPlugin> … … 11 78 </energyEstimationPlugin> 12 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 --> 13 84 <powerProfile> 14 85 <parameter name="pState"> … … 17 88 </property> 18 89 <property name="frequency"> 19 <value >3000</value>90 <value >3000</value> 20 91 </property> 21 92 <property name="voltage"> … … 43 114 </profile> 44 115 </computingResource> 45 <energyEstimationPlugin>46 <name>ComputingNodeEnergyEstimationPlugin</name>47 </energyEstimationPlugin>48 <profile>49 <powerProfile>50 <powerStates>51 <powerState>52 <name>ON</name>53 <powerUsage>20</powerUsage>54 <transition>55 <to>OFF</to>56 <powerUsage>30</powerUsage>57 <time>30</time>58 </transition>59 </powerState>60 <powerState>61 <name>OFF</name>62 <powerUsage>0</powerUsage>63 <transition>64 <to>ON</to>65 <powerUsage>40</powerUsage>66 <time>60</time>67 </transition>68 </powerState>69 </powerStates>70 </powerProfile>71 <airThroughputProfile>72 <airThroughputState>73 <name>mode1</name>74 <value>105</value>75 <powerUsage>10.3</powerUsage>76 </airThroughputState>77 <airThroughputState>78 <name>mode2</name>79 <value>110</value>80 <powerUsage>10.9</powerUsage>81 </airThroughputState>82 <airThroughputState>83 <name>mode3</name>84 <value>115</value>85 <powerUsage>11.4</powerUsage>86 </airThroughputState>87 <airThroughputState>88 <name>mode4</name>89 <value>120</value>90 <powerUsage>12.1</powerUsage>91 </airThroughputState>92 </airThroughputProfile>93 </profile>94 116 </computingResource> 95 117 </computingResource> 96 118 </computingResource> 97 119 98 <scheduler class="Cluster" id="cluster">120 <scheduler class="Cluster" name="cluster"> 99 121 <schedulingPlugin> 100 122 <name>FCFSLocalSchedulingPlugin</name> 101 123 </schedulingPlugin> 102 <managedComputingResource include="true">103 <resource Id>rack1</resourceId>104 <resource Id>rack2</resourceId>105 <resource Id>rack3</resourceId>106 <resource Id>rack4</resourceId>107 </managedComputingResource >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> 108 130 </scheduler> 109 131
Note: See TracChangeset
for help on using the changeset viewer.
