Changeset 329 for xssim/trunk/src/test/rewolucja/schemas/example/coolemall
- Timestamp:
- 07/19/12 07:57:32 (13 years ago)
- Location:
- xssim/trunk/src/test/rewolucja/schemas/example/coolemall
- Files:
-
- 3 edited
-
example2.xml (modified) (3 diffs)
-
example4.xml (modified) (4 diffs)
-
example7.xml (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
-
xssim/trunk/src/test/rewolucja/schemas/example/coolemall/example2.xml
r326 r329 79 79 <profile> 80 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 81 According to it, processor can operate in two p-states: P0 and P1 82 P0 p-state is characterized by operating frequency - 3000, 83 voltage level - 1.3 and power usage - 35. 84 Next p-state - P1 has the following values: 2666, 1.1, 30 respectively. 83 85 --> 84 86 <powerProfile> … … 93 95 <value>1.3</value> 94 96 </property> 95 <property name="power ">97 <property name="powerUsage"> 96 98 <value>35</value> 97 99 </property> … … 107 109 <value>1.1</value> 108 110 </property> 109 <property name="power ">111 <property name="powerUsage"> 110 112 <value>30</value> 111 113 </property> -
xssim/trunk/src/test/rewolucja/schemas/example/coolemall/example4.xml
r326 r329 4 4 5 5 <resources> 6 <description> 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 to vector (6, 0, 2) 10 Rack1 contains 2 computing nodes - node11 and node22. Appropriate coordinates for node11 are (0, 0, 0) 11 and for node12 (0, 1, 0). Rack2 contains 2 computing nodes named node21 and node22. Their location is defined as follows: 12 (0, 0, 0) for node21 and (1, 0, 0) for node22. 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 precedent computing resource. Moreover, it is possible to define only the arrangement of 15 the computing resources by increasing only the value of one coordinate. 16 In the following example, racks location is defined using relative positions (with respect to the data center), while 17 for nodes the order of appearance is specified (with additional direction in which the order tends 18 (node12 is located after node11 and placed above it, while node22 is located on the right side of node21) 19 It has to be stressed that simulator only stores the location parameters and does not process them. Hence, their interpretation should be done by user. 20 </description> 6 21 <computingResource class="DataCenter" name="dataCenter"> 7 22 <computingResource class="Rack" name="rack1"> 8 23 <location> 24 <horizontal>4</horizontal> 9 25 <vertical>0</vertical> 10 <horizontal>4</horizontal>11 26 <depth>2</depth> 12 27 </location> 13 28 <computingResource class="ComputingNode" name="node11"> 14 29 <location> 30 <horizontal>0</horizontal> 15 31 <vertical>0</vertical> 16 <horizontal>0</horizontal>17 32 <depth>0</depth> 18 33 </location> … … 20 35 <computingResource class="ComputingNode" name="node12"> 21 36 <location> 37 <horizontal>0</horizontal> 22 38 <vertical>1</vertical> 23 <horizontal>0</horizontal>24 39 <depth>0</depth> 25 40 </location> … … 28 43 <computingResource class="Rack" name="rack2"> 29 44 <location> 45 <horizontal>6</horizontal> 30 46 <vertical>0</vertical> 31 <horizontal>6</horizontal>32 47 <depth>2</depth> 33 48 </location> 34 49 <computingResource class="ComputingNode" name="node21"> 35 50 <location> 51 <horizontal>0</horizontal> 36 52 <vertical>0</vertical> 37 <horizontal>0</horizontal>38 53 <depth>0</depth> 39 54 </location> … … 41 56 <computingResource class="ComputingNode" name="node22"> 42 57 <location> 58 <horizontal>1</horizontal> 43 59 <vertical>0</vertical> 44 <horizontal>1</horizontal>45 60 <depth>0</depth> 46 61 </location> -
xssim/trunk/src/test/rewolucja/schemas/example/coolemall/example7.xml
r326 r329 4 4 5 5 <resources> 6 <description> 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. 10 Rack1 contains 2 computing nodes - node11 and node22, described in common way. 11 Nodes in rack2 are defined using template. Node21 refers to template modelNodeA, 12 and thus will be created with respect to the specification given in that template. 13 Node22 contains 8 processors which definition is included in modeProcessorB template. 14 </description> 6 15 <computingResource class="DataCenter" name="dataCenter"> 7 16 <computingResource class="Rack" name="rack1"> … … 33 42 34 43 <templates> 44 <description> 45 There are two processor templates named modelProcessorA (with speed 2) and modelProcessorB (with speed 1). 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. 48 </description> 35 49 <computingResourceTemplate class="ComputingNode" name="modelNodeA"> 36 50 <computingResource class="Processor" count="4"> … … 39 53 </computingResourceTemplate> 40 54 <computingResourceTemplate class="Processor" name="modelProcessorA"> 55 <parameter name="Speed"> 56 <value>2</value> 57 </parameter> 41 58 </computingResourceTemplate> 42 59 <computingResourceTemplate class="Processor" name="modelProcessorB"> 60 <parameter name="Speed"> 61 <value>1</value> 62 </parameter> 43 63 </computingResourceTemplate> 44 64 </templates>
Note: See TracChangeset
for help on using the changeset viewer.
