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

More documents

Recommendations

Info

46 CHAPTER 4. PERFORMANCE ENGINEERING OF EVENT-BASED SYSTEMS Pattern 2: Standard Pub/Sub - Fixed Number of Subscribers 1‘Event! " n‘Notification 1‘Event 1‘Event 1‘Notification T2 Create Notifications 1‘Notification Producer T1 Publish Event Broker T3 Forward Event Consumers Transition 2 In T2, for every incoming event n notifications are created. Broker Event 1 n Broker Not. Figure 4.8: Standard Pub/Sub Pattern - Fixed Number of Subscribers Characteristics • 1 : n communication (one event is consumed by n consumers) Example A fixed number of event consumers subscribe to a topic. Description A producer publishes an event, which is received by a broker. The broker notifies the event consumers (e.g. subscribers of a topic) by sending a notification event to them. The idea of this pattern is based on the presumption that the service demand per event on the broker is composed of two parts, the service demand needed for every incoming event and the aggregated service demands for the notification of the subscribers: 1‘Conf.No 1‘Conf.No S EventT otal,Broker = S Event,Broker + n · S Notification,Broker (4.19) Init T0 Controller T2‘ where Configure Controlller Creates the configured no. n : No. of event notifications. of notifications per Event. S Event,Broker : Service demand for receiving and processing incoming message. 1‘Event 1‘Event 1‘Notification 1‘Notification S Notification,Broker : Service demand of broker to create, process and send notifications. We implement the Producer T1 service demand in our patterns by using two Broker T3 different token colors, one for the general service Consumers Publish costs Event (event) and one for the notifications Forward (notification) Event created by the broker. Therefore each incoming event is represented by one token event and n tokens of the color notification, where n is the number of consumers. In this version of the pattern, we implemented a straight-forward approach for a 1:n communication. The number of consumers is directly set in the cardinality of the transition (see Figure 4.8). The downside of this approach is, that the number of consumers is fixed in the transition and therefore cannot be modified without changing the transition (and therefore the structure of the model). The reason is that cardinality of transitions in standard QPNs is defined as constant number. To add more flexibility we propose to allow not only constants but also, e.g., distribution functions (see Section 4.3).
4.2. PERFORMANCE MODELING PATTERN 47 QPN Definition Places: Place Type Description Producer S Publish events. Broker Q Receives all incoming events and forwards notifIcation events to n consumers. Consumer S Consumes incoming events. Colors: Color Event Notification (Not.) Description Represents the published event. Event notification. Transitions: Id Input Output Description T1 1 Event (Producer) 1 Event (Broker) Producer publishes event. T2 1 Event (Broker) n Notifications (Broker) Notifications are created. T3 1 Notification (Broker) 1 Not. (Consumer) Consumer receives event.
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 59: 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 111 and 112:
5.1. SPECJMS2007 - A STANDARD BENCH
Page 113 and 114:
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

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

Delete template?

Save as template?