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

More documents

Recommendations

Info

64 CHAPTER 4. PERFORMANCE ENGINEERING OF EVENT-BASED SYSTEMS used a single color (Trigger) to model the pull attempt of the consumer and its resources. In this pattern, we use two colors to model these aspects: 1. Trigger: responsible to trigger pull attempt. 2. Slot: represents available resources of consumer. The Trigger token controls if and when the consumer establishes a connection to the broker. The pull attempt of the consumer is modeled by transition T2 : if an Event, a Trigger and a Slot (standing for free resources) exist, the consumer pulls an Event. The consumer tries to pull Events (by firing transition T2 ) until no further resources (Slots) or Events are available in the depository of the Store respectively the Broker: • If no further resources are available, the consumer disconnects and waits for resources to be released (see transition T3 ) before establishing a new connection. • If there are free resources (Slot tokens) available but no further Event token available, the consumer closes the connection and waits for ceratin time interval before he reconnects (see transitions T4 & T5 ). All places and transitions are illustrated in Figure 4.16. The number of initial Slot tokens in the ordinary place Store defines, how many events the consumer is able to handle in parallel, e.g., the number of service places. QPN Definition Places: Place Type Description Producer S Publishes an event. Broker S Stores incoming events. Timer Q Timer queue (scheduling strategy: infinite server). Store O Stores trigger and slot tokens. Used to model free resources. Consumer S Consumes events.
4.2. PERFORMANCE MODELING PATTERN 65 Colors: Color Event Trigger Slot Sleep Description Represents the published event. Triggers pull commands. Represents resources of consumer. Exists for time interval the consumer waits after an unsuccessful pull attempt before reconnecting. Init No. of Colors: Color Place Count Description Trigger Store 1 Slot Store j j is equal to the number of events the consumer can process in parallel. Transitions: Id Input Output FW Description T1 1 Event (P roducer) 1 Event (Broker) 1 Producer publishes an event. T2 1 Event (Broker) 1 Event (Consumer) Consumer pulls 1 Trigger (Store) 1 Trigger (Store) ∞ an event. 1 Slot (Store) T3 1 Event (Consumer) 1 Slot (Store) 1 After an event is processed the consumer releases the resources. T4 1 Trigger (Store) 1 Slot (Store) 1 If no event is 1 Slot (Store) 1 Sleep (T imer) available, disconnect and wait for a specified time interval. T5 1 Sleep (T imer) 1 Trigger (Store) 1 After a specified time interval, the consumer wakes up to pull events.
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 77: 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?