Performance Modeling and Benchmarking of Event-Based ... - DVS

More documents

Recommendations

Info

50 CHAPTER 4. PERFORMANCE ENGINEERING OF EVENT-BASED SYSTEMS The Controller place is in state A which is represented by a State A token stored in the depository. After the system initialization, the following tokens exist in the system: Place Color Count Note Controller State A 1 Init value. Controller Subscriber A n Received via T0. 2. Creation of Notifications (a) Producer Publishes Event The producer publishes an Event token, which arrives via T1 at the broker. After the broker received the Event token, the transition T2-II is fired and changes the state of the Controller from A to B by replacing the State A token with a State B token. Place Color Count Note Controller State B 1 Produced by T2. Controller Subscriber A n (b) Notification of Subscribers Since the Controller place is now state B, transition T2-IV is fired for each of the n Subscriber A tokens and transforms them as illustrated in Figure 4.10(b) into Notification tokens (sent to the Broker) and into Subscriber B tokens stored in the Controller, respectively. These Notification tokens will be processed by the Broker and afterwards delivered to the consumers. Therefore, each Event token triggers the generation of n Notifications. Place Color Count Note Controller State B 1 Controller Subscriber B n Broker Notification n To be forwarded to the consumer. QPN Definition Places: Place Type Description Producer S Publishes events. Broker Q Receives all incoming events and forwards notifications to the consumers. Consumer S Consumes incoming events. Controller O Controls the creation of Notification token. Init O Central place for the configuration. Note The Init place can be used to configure the number of subscribers of different interactions. Colors:
4.2. PERFORMANCE MODELING PATTERN 51 Color Description Event Represents the published event. Notification (Not.) Event notification. State A Exists only if Controller is in state A. State B Exists only if Controller is in state B. Subscriber A (Sub. A) Each Sub. A stands for a notification, which will be generated after the state of the Controller place changes to state B. Subscriber B (Sub. B) Each Sub. B stands for a notification, which will be generated after the state of the Controller place changes to state A. Subscriber Is used to initialize the number of subscribers. Each token represents one subscriber. Init No. of Colors: Color Place No. Description State A Controller 1 At the beginning the Controller place is in state A. Subscriber Init n One token for each consumer.
Page 1:
Performance Modeling and Benchmarki
Page 4 and 5:
priorities. Finally, we validated o
Page 6 and 7:
4.3.4 Tool Extension . . . . . . .
Page 8 and 9:
5.7 Proportions of the Interactions
Page 11 and 12:
List of Acronyms Acronym λ t,k j A
Page 13 and 14: Acronym SPEC-OSG SPE SPN SQL ST SUT
Page 15 and 16: Chapter 1 Introduction 1.1 Motivati
Page 17 and 18: PC Server 310 PC Server 310 PC Serv
Page 19 and 20: 1.3. APPROACH AND CONTRIBUTIONS OF
Page 21 and 22: 1.4. THESIS ORGANIZATION 7 • Stan
Page 23 and 24: Chapter 2 Background In this chapte
Page 25 and 26: 2.1. EVENT-BASED SYSTEMS 11 is gene
Page 27 and 28: 2.2. TECHNOLOGY PLATFORMS OF EVENT-
Page 35 and 36: 2.3. INTRODUCTION TO QUEUEING PETRI
Page 37 and 38: 2.3. INTRODUCTION TO QUEUEING PETRI
Page 39 and 40: Chapter 3 Related Work In this chap
Page 41 and 42: 3.2. BENCHMARKING OF EVENT-BASED SY
Page 43 and 44: 3.2. BENCHMARKING OF EVENT-BASED SY
Page 45 and 46: 3.4. CONCLUDING REMARKS 31 hierarch
Page 47 and 48: Chapter 4 Performance Engineering o
Page 49 and 50: 4.1. MODELING METHODOLOGY FOR EBS 3
Page 57 and 58: 4.2. PERFORMANCE MODELING PATTERN 4
Page 63: 4.2. PERFORMANCE MODELING PATTERN 4
Page 87 and 88: 4.3. EXTENSIONS OF QPNS 73 ,-).$%&'
Page 89 and 90: 4.4. CONCLUDING REMARKS 75 Without
Page 91 and 92: Chapter 5 Benchmarking of Event-Bas
Page 93 and 94: 5.1. SPECJMS2007 - A STANDARD BENCH
Page 115 and 116:
5.2. CASE STUDY I: SPECJMS2007 101
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
5.3. JMS2009-PS - A PUBLISH /SUBSCR
Page 127 and 128:
5.3. JMS2009-PS - A PUBLISH /SUBSCR
Page 129 and 130:
5.4. CASE STUDY II: JMS2009-PS 115
Page 131 and 132:
5.4. CASE STUDY II: JMS2009-PS 117
Page 133 and 134:
Chapter 6 Performance Modeling of E
Page 135 and 136:
6.2. MODELING SPECJMS2007 121 Scena
Page 137 and 138:
6.2. MODELING SPECJMS2007 123 BASE*
Page 139 and 140:
6.2. MODELING SPECJMS2007 125 1‘O
Page 141 and 142:
6.2. MODELING SPECJMS2007 127 Sc. 1
Page 143 and 144:
6.2. MODELING SPECJMS2007 129 Perce
Page 145 and 146:
6.2. MODELING SPECJMS2007 131 Serve
Page 147 and 148:
6.3. CONCLUDING REMARKS 133 the mod
Page 149 and 150:
Chapter 7 Conclusions and Outlook W
Page 151 and 152:
7.1. ONGOING AND FUTURE WORK 137 JA
Page 153 and 154:
7.1. ONGOING AND FUTURE WORK 139 th
Page 155 and 156:
Bibliography [1] J. Abbott, K. B. M
Page 157 and 158:
BIBLIOGRAPHY 143 [29] BiCEP Researc
Page 159 and 160:
BIBLIOGRAPHY 145 [61] G. Cugola and
Page 161 and 162:
BIBLIOGRAPHY 147 [92] R. Henjes, M.
Page 163 and 164:
BIBLIOGRAPHY 149 [128] S. Kounev an
Page 165 and 166:
BIBLIOGRAPHY 151 [162] Object Compu
Page 167 and 168:
BIBLIOGRAPHY 153 [197] K. Sachs, S.
Page 169 and 170:
BIBLIOGRAPHY 155 [228] P. Tran, P.
Page 171:
Erklärung Hiermit erkläre ich, di
show all

Performance Modeling and Benchmarking of Event-Based ... - DVS

Create successful ePaper yourself

Delete template?

Save as template?