Changeset 349 for xssim/trunk/src/test/rewolucja/schemas/example/coolemall
- Timestamp:
- 07/20/12 09:49:08 (13 years ago)
- Location:
- xssim/trunk/src/test/rewolucja/schemas/example/coolemall
- Files:
-
- 5 edited
-
example1.xml (modified) (2 diffs)
-
example2.xml (modified) (6 diffs)
-
example3.xml (modified) (1 diff)
-
example4.xml (modified) (1 diff)
-
example7.xml (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
-
xssim/trunk/src/test/rewolucja/schemas/example/coolemall/example1.xml
r337 r349 9 9 <resources> 10 10 <description> 11 This basic example defines simple resource hierarchy within a single data center (named dataCenter). It consist of 4 racks11 This basic example defines simple resource hierarchy within a single data center (named dataCenter). It consists of 4 racks 12 12 (with names created according to the name attribute and subsequent natural number: rack_0, rack_1, rack_2 and rack_3). 13 13 Each of them contains 64 computing nodes (names will be generated using resource class and subsequent natural number: … … 29 29 </resourceUnit> 30 30 <computingResource class="Processor" count="2"> 31 <parameter name=" Speed">31 <parameter name="speed"> 32 32 <value>2</value> 33 33 </parameter> -
xssim/trunk/src/test/rewolucja/schemas/example/coolemall/example2.xml
r344 r349 5 5 <description> 6 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.7 Simulated architecture consists of data center with 4 racks. Each of them contains 64 computing nodes with 2 processors. 8 8 Speed of every processor is equal 2. All computing nodes have 12GB of memory and 4TB storage. 9 9 For the detailed energy characteristics description, see the following comments. … … 18 18 <!-- Definition of computing node power profile 19 19 According to it, there are two supported power states: ON and OFF 20 Computing node in ON state consume 20 watts, while in OFF state 0.21 Transition between ON and OFF state takes 30 seconds an tconsumes 30 watts,22 while in the opposite energy consumption rate is equal 40 watts over 60 seconds.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. 23 23 --> 24 24 <powerProfile> … … 31 31 <powerState> 32 32 <name>ON</name> 33 <powerUsage unit=" watts">20</powerUsage>33 <powerUsage unit="W">20</powerUsage> 34 34 <transition> 35 35 <to>OFF</to> 36 <powerUsage unit=" watts">30</powerUsage>37 <time unit="s econds">30</time>36 <powerUsage unit="W">30</powerUsage> 37 <time unit="s">30</time> 38 38 </transition> 39 39 </powerState> 40 40 <powerState> 41 41 <name>OFF</name> 42 <powerUsage unit=" watts">0</powerUsage>42 <powerUsage unit="W">0</powerUsage> 43 43 <transition> 44 44 <to>ON</to> 45 45 <powerUsage unit="watts">40</powerUsage> 46 <time unit="s econds">60</time>46 <time unit="s">60</time> 47 47 </transition> 48 48 </powerState> … … 57 57 <name>mode1</name> 58 58 <value unit="m3/h">105</value> 59 <powerUsage unit=" watts">10.3</powerUsage>59 <powerUsage unit="W">10.3</powerUsage> 60 60 </airThroughputState> 61 61 <airThroughputState> 62 62 <name>mode2</name> 63 63 <value unit="m3/h">110</value> 64 <powerUsage unit=" watts">10.9</powerUsage>64 <powerUsage unit="W">10.9</powerUsage> 65 65 </airThroughputState> 66 66 <airThroughputState> 67 67 <name>mode3</name> 68 68 <value unit="m3/h">115</value> 69 <powerUsage unit=" watts">11.4</powerUsage>69 <powerUsage unit="W">11.4</powerUsage> 70 70 </airThroughputState> 71 71 <airThroughputState> 72 72 <name>mode4</name> 73 73 <value unit="m3/h">120</value> 74 <powerUsage unit=" watts">12.1</powerUsage>74 <powerUsage unit="W">12.1</powerUsage> 75 75 </airThroughputState> 76 76 </airThroughputStates> … … 95 95 </property> 96 96 <property name="frequency"> 97 <value unit=" hertz">3000</value>97 <value unit="Hz">3000</value> 98 98 </property> 99 99 <property name="voltage"> 100 <value unit=" volt">1.3</value>100 <value unit="V">1.3</value> 101 101 </property> 102 102 <property name="powerUsage"> 103 <value unit=" watts">35</value>103 <value unit="W">35</value> 104 104 </property> 105 105 </parameter> … … 109 109 </property> 110 110 <property name="frequency"> 111 <value unit=" hertz">2666</value>111 <value unit="H`">2666</value> 112 112 </property> 113 113 <property name="voltage"> 114 <value unit=" volt">1.1</value>114 <value unit="V">1.1</value> 115 115 </property> 116 116 <property name="powerUsage"> 117 <value unit=" watts">30</value>117 <value unit="W">30</value> 118 118 </property> 119 119 </parameter> -
xssim/trunk/src/test/rewolucja/schemas/example/coolemall/example3.xml
r344 r349 26 26 </resourceUnit> 27 27 <computingResource class="Processor" type="i7"> 28 <profile> 29 <powerProfile> 30 <parameter name="pState"> 31 <property name="name"> 32 <value>P0</value> 33 </property> 34 <property name="frequency"> 35 <value >3000</value> 36 </property> 37 <property name="voltage"> 38 <value>1.3</value> 39 </property> 40 <property name="powerUsage"> 41 <value>35</value> 42 </property> 43 </parameter> 44 <parameter name="pState"> 45 <property name="name"> 46 <value>P1</value> 47 </property> 48 <property name="frequency"> 49 <value>2666</value> 50 </property> 51 <property name="voltage"> 52 <value>1.1</value> 53 </property> 54 <property name="powerUsage"> 55 <value>30</value> 56 </property> 57 </parameter> 58 </powerProfile> 59 </profile> 28 <parameter name="speed"> 29 <value>2</value> 30 </parameter> 60 31 <computingResource class="Core" count="4"/> 61 32 </computingResource> -
xssim/trunk/src/test/rewolucja/schemas/example/coolemall/example4.xml
r335 r349 6 6 <description> 7 7 This short example presents how to describe computing resource location. 8 Simulated architecture consist of data center with 2 racks named rack1 and rack2, respectively.9 Location of rack1 is defined using vector (4, 0, 2), while rack2 according tovector (6, 0, 2)8 Simulated architecture consists of data center with 2 racks named rack1 and rack2, respectively. 9 Location of rack1 is defined using vector (4, 0, 2), while rack2 using vector (6, 0, 2) 10 10 Rack1 contains 2 computing nodes - node11 and node12. Appropriate coordinates for node11 are (0, 0, 0) 11 11 and for node12 (0, 1, 0). Rack2 contains 2 computing nodes named node21 and node22. Their location is defined as follows: 12 12 (0, 0, 0) for node21 and (1, 0, 0) for node22. 13 13 Using 3 coordinates allows to express location in various ways. It can be interpreted as a absolute placement in 3D, as well as the 14 relative position according to the p recedent computing resource. Moreover, it is possible to define only the arrangement of14 relative position according to the parent computing resource. Moreover, it is possible to define only the arrangement of 15 15 the computing resources by increasing only the value of one coordinate. 16 16 In the following example, racks location is defined using relative positions (with respect to the data center), while -
xssim/trunk/src/test/rewolucja/schemas/example/coolemall/example7.xml
r337 r349 6 6 <description> 7 7 The goal of this example is to introduce the templates usage. 8 It focus on showing that appropriate templates may be included in various computing resource levels and moreover can be formed using other templates.9 Simulated architecture consist of data center with 2 racks named rack1 and rack2 respectively.8 It focuses on showing that appropriate templates may be included on various computing resource levels and moreover can be formed using other templates. 9 Simulated architecture consists of data center with 2 racks named rack1 and rack2 respectively. 10 10 Rack1 contains 2 computing nodes - node11 and node12, described in common way. 11 11 Nodes in rack2 are defined using template. Node21 refers to template modelNodeA and, … … 45 45 There are two processor templates named modelProcessorA (with cpu speed 2) and modelProcessorB (with cpu speed 1). 46 46 There is also one computing node template denoted as modelNodeA, which contains 4 processors that refer to modelProcessorA template. 47 That means that the given processors will be created according to the guidelines defined in template modelProcessorA (they will have speed equal 2).47 That means that the given processors will be created according to the characteristics defined in template modelProcessorA (they will have speed equal 2). 48 48 </description> 49 49 <computingResourceTemplate class="ComputingNode" name="modelNodeA"> … … 53 53 </computingResourceTemplate> 54 54 <computingResourceTemplate class="Processor" name="modelProcessorA"> 55 <parameter name=" Speed">55 <parameter name="speed"> 56 56 <value>2</value> 57 57 </parameter> 58 58 </computingResourceTemplate> 59 59 <computingResourceTemplate class="Processor" name="modelProcessorB"> 60 <parameter name=" Speed">60 <parameter name="speed"> 61 61 <value>1</value> 62 62 </parameter>
Note: See TracChangeset
for help on using the changeset viewer.
