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

More documents

Recommendations

Info

66 CHAPTER 4. PERFORMANCE ENGINEERING OF EVENT-BASED SYSTEMS Pattern 8: Time Window !1‘Disconnect T3 1‘Connected" 1‘Connect" Connection Timer 1‘Disconnect" !1‘Connect Broker T2 1‘Event 1‘Event T1 Consumer T2: Disconnect Timer Disconnect Connection Connected 1 1 1 Timer Connect T1: Consume Event Broker 1 Event 1 Connection Connected 1 1 Consumer Event Connection Conne cted T3: Connect Timer Connect Timer Disconne ct Connection Connected Figure 4.17: Standard Queue Pattern Characteristics • Time-controlled • Modeling of a time window • Modeling of connections Example An event consumer connects to a broker to receive events, stays online for a specified interval (time window) and disconnects afterwards, e.g., a consumer connects every hour for five minutes to a broker to receive events. Description In the previous pattern, we implemented a consumer who connects to the broker, pulls events and immediately disconnects. In this pattern, we handle another situation in which the consumer connects and stays online for specified a period. Therefore, we present a way to model a connection with two states (connected and disconnected) in this pattern. The state change is triggered by two colors named Connect respectively Disconnect. The Connection itself is modeled by an ordinary place. If the Consumer has established a connection (transition T3 ), a token Connected is stored in the Connection place and a Disconnect token is sent to the Timer. The Timer controls the time between the state changes: the time a consumer stays connected (disconnected) is equal to the service demand of the Disconnect token (Connect token) of the Timer place. As soon as the Consumer disconnects (triggered by an Disconnect token), the Connected token is removed from the Connection place by transition
4.2. PERFORMANCE MODELING PATTERN 67 T2. As illustrated in Figure 4.17, Events are only pushed to the Consumer by the transition T1 if a Connected token exists. QPN Definition Places: Place Type Description Broker S Responsible for forwarding events to the consumer. Connection O Represents the state of connection. If a Connected token is stored inside, the consumer is connected. Consumer S Consumes incoming events. Colors: Color Event Connected Connect Disconnect Description Represents the published event. Only exists if connection is active. Triggers to establish a connection. Triggers the consumer to disconnect. Init No. of Colors: It is possible to configure the model in two ways: either the consumer is connected and disconnects immediately or the consumer establishes a connections as first action: The Consumer is connected and disconnects: Color Place Count Connected Trigger 1 Disconnect Timer 1 The Consumer establishes a connection: Color Place Count Connect Timer 1 Transitions: Id Input Output FW Description T1 1 Event (Broker) 1 Event (Consumer) 1 An event is forwarded 1 Connect (Conn.) 1 Connected (Conn.) 1 to the consumer. T2 1 Disconnect (T imer) 1 Connect (Conn.) 1 Closes connection and 1 Connected (Conn.) 1 triggers reconnection. T3 1 Connect (T imer) 1 Disconnect (Conn.) 1 Opens connection and 1 Connected (Conn.) 1 triggers disconnection.
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 29 and 30: 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 79: 4.2. PERFORMANCE MODELING PATTERN 6
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 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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?