3.1 MB - Evernote

More documents

Recommendations

Info

Implementation mode. A cancelback strategy was already mentioned by David Jefferson [17] but the cancelback strategy used here will differ slightly from the one suggested by him. When the LP operates in cancelback mode then it will still respond to control messages and will still receive Transactions from other LPs but it will stop moving or processing any local Transaction so that no simulation progress is made by the LP and no simulation state information are saved as a result. Further the LP will attempt to cancel back Transactions that it received from other LPs in order to free memory or at least stop memory usage growing further. To cancelback a Transaction means that all local traces that a Transaction was received are removed and the Transaction is sent back to its original sender that will rollback to the move time of that Transaction. The main methods involved with the cancelback mechanism are the method LogicalProcess.needToCancelBackTransactions() which is called by an LP that is in cancelback mode and the method LogicalProcess.cancelBackTransaction() which is used to send a cancelled Transaction back to the sender LP. This cancelback mechanism of the parallel simulator is not only used for the general memory management but also when the Actuator value of the LPCC has been exceeded. 5.3.5 Logging The parallel simulator uses the Java logging library log4j [3] for its logging and standard user output. It is the same logging library that is used by ProActive. The log4j library makes it possible to enable or disable parts or all of the logging or to change the detail of logging by means of a configuration file without any changes to the Java code. To utilise the same logging library for ProActive and the parallel simulator means that only a single configuration file can be used to configure the logging output for both. A hierarchical structure of loggers combined with inheritance between loggers makes it very easy and fast to configure the logging of the simulator. A detailed description of the log4j library and its configuration can be found at [3]. The specific loggers used by the parallel simulator are described in Appendix C. As mentioned above the parallel simulator will use the same log4j configuration file like ProActive. By default this is the file proactive-log4j but a different file can be specified as described in the ProActive documentation [15]. The log4j root logger for all output from the parallel simulator is parallelJavaGpssSimulator (in the log4j configuration file all loggers have to be prefixed with “log4j.logger.” so that this logger would appear as 69
70 Implementation log4j.logger.parallelJavaGpssSimulator). A hierarchy of lower level loggers allow the configuration of which information will be output or logged by the parallel simulator. The log4j logging library supports the inheritance of logger properties, which means that a lower level logger that is not specifically configured will inherit the configuration from a logger at a higher level within the same name space. For example if only the logger parallelJavaGpssSimulator is configured then all other loggers of the parallel simulator would inherit the same configuration settings from it. 5.4 Running the Parallel Simulator 5.4.1 Prerequisites The parallel GPSS simulator was implemented using the Java TM 2 Platform Standard Edition 5.0, also known as J2SE5.0 or Java 1.5 [31] and ProActive version <strong>3.1</strong> [15] as the Grid environment. J2SE5.0 or the JRE of the same version plus ProActive <strong>3.1</strong> need to be installed on all nodes that are supposed to be used by the parallel GPSS simulator. The parallel simulator might also work with later versions of the Java Runtime Environment and ProActive as long as these are backwards compatible but the author of this work can give no guarantees in this respect. Because the parallel simulator and the libraries it uses are written in Java it can be run on many different platforms. But the main target platforms of this work are Unix based systems because the scripts that are part of the parallel simulator are only provided as Unix shell scripts. These relatively basic scripts will need to be rewritten before the parallel simulator can be used on Windows or other non-Unix based platforms. 5.4.2 Files The following files are required or are optionally needed in order to run the parallel simulator. They can be found in the folder /ParallelJavaGpssSimulator/ on the attached CD and will briefly be described here. deploymentDescriptor.xml This is the ProActive deployment descriptor file mentioned in 3.2.1. It is read by ProActive to determine which nodes the parallel simulator should use and how these
Page 1 and 2:
TRANSACTION-ORIENTED SIMULATION IN
Page 3 and 4:
Table of Content II Table of Conten
Page 5 and 6:
IV Table of Content 6 VALIDATION OF
Page 7 and 8:
Figures VI Figures Figure 1: Ad Hoc
Page 9 and 10:
Tables VIII Tables Table 1: Change
Page 11 and 12:
2 Introduction synchronisation algo
Page 13 and 14:
2 Fundamental Concepts Fundamental
Page 15 and 16:
Figure 1: Ad Hoc Grid architecture
Page 17 and 18:
8 Fundamental Concepts In continuou
Page 19 and 20:
10 Fundamental Concepts Two other a
Page 21 and 22:
12 Fundamental Concepts known as st
Page 23 and 24:
14 Fundamental Concepts event execu
Page 25 and 26:
3 Ad Hoc Grid Aspects 16 Ad Hoc Gri
Page 27 and 28: 18 Ad Hoc Grid Aspects resources an
Page 29 and 30: 20 Ad Hoc Grid Aspects means that a
Page 31 and 32: Parallel Transaction-oriented Simul
Page 33 and 34: 24 Parallel Transaction-oriented Si
Page 35 and 36: 4.2 Synchronisation algorithm 26 Pa
Page 49 and 50: 5 Implementation 40 Implementation
Page 51 and 52: 42 Implementation confirm a provisi
Page 53 and 54: 44 Implementation large numerical p
Page 55 and 56: 46 Implementation A detailed descri
Page 57 and 58: 48 Implementation But in a parallel
Page 59 and 60: 50 Implementation GPSS test models
Page 61 and 62: Simulation Controller side 52 Imple
Page 63 and 64: 54 Implementation technique describ
Page 65 and 66: Implementation Euclidean distance b
Page 67 and 68: 58 Implementation chain at the corr
Page 69 and 70: 60 Implementation The algorithm wil
Page 71 and 72: No Start Is Active Object body acti
Page 73 and 74: 5.3.2 GVT Calculation and End of Si
Page 75 and 76: 66 Implementation provisional simul
Page 77: Implementation relatively basic per
Page 81 and 82: proactive-log4j 72 Implementation T
Page 83 and 84: 74 Implementation Memory Allocation
Page 85 and 86: 76 Validation of the Parallel Simul
Page 93 and 94: 6.4 Validation 4 84 Validation of t
Page 97 and 98: … LpccEnabled=true LpccClusterNum
Page 99 and 100: Validation 5.2 Validation of the Pa
Page 105 and 106: 7 Conclusions 96 Conclusions Even s
Page 107 and 108: References 98 References [1] Amin K
Page 109 and 110: [19] Krafft G. Parallelisation of T
Page 111 and 112: Appendix A: Detailed GPSS Syntax 10
Page 113 and 114: Reserved word: DEPART Syntax: [] DE
Page 115 and 116: Reserved word: SEIZE Syntax: [] SEI
Page 117 and 118: Setting: LpccClusterNumber Default
Page 119 and 120: Appendix C: Simulator log4j loggers
Page 121 and 122: Logger: parallelJavaGpssSimulator.l
Page 123 and 124: 114 Appendix D: Structure of the at
Page 125 and 126: Appendix E: Documentation of select
Page 127 and 128: Appendix E: Documentation of select
Page 129 and 130:
Appendix E: Documentation of select
Page 131 and 132:
!"#"$$%$&"'"(!))*+,-$"./#0$! 1$"))
Page 133 and 134:
Page 135 and 136:
!/+/.7/8$ Appendix E: Documentation
Page 137 and 138:
Returns: Appendix E: Documentation
Page 139 and 140:
!"#$%&''$()*)")$ +',)$-)$. #,/. !"#
Page 141 and 142:
!"#$%&'()#%*+,"-*.# Appendix E: Doc
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Constructor Detail !"#$%&'$(#$)*$%+
Page 155 and 156:
Page 157 and 158:
Validation 1.1, output of simulate:
Page 159 and 160:
Validation 2, output of LP: Appendi
Page 161 and 162:
Appendix F: Validation output logs
Page 163 and 164:
Validation 2, output of simulate: A
Page 165 and 166:
Validation 3.1, output of LP1: Appe
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Validation 4, output of LP1: Append
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
simulation for time 2000) (628) 20:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Validation 4, output of simulate: A
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
(135) 19:37:56,477 Total transactio
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
(68) 19:37:56,619 by the transactio
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
(1295) 14:25:22,740 Simulation stop
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
(68) 14:25:22,888 by the transactio
Page 239 and 240:
Validation 6.2, output of LP2: (1)
Page 241:
(32) (1,2) 0 765 Block: TRANSFER 0.
show all

3.1 MB - Evernote

Create successful ePaper yourself

Delete template?

Save as template?