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

More documents

Recommendations

Info

68 CHAPTER 4. PERFORMANCE ENGINEERING OF EVENT-BASED SYSTEMS Pattern 9: Random Load Balancer ... ... ... Load Balancer Load Balancer T1 ... Consumer 1 Consumer 2 Consumer n T1: Random Load Balancer Event 1 1 1 1 1 1 Consumer 1 Event Consumer 2 Event Consumer n Event Figure 4.18: Load Balancer - Random Characteristics • Load balancing • Random load distribution (uniformly distributed) Example Incoming events are distributed uniformly among consumers by a load balancer. Each event is forwarded to exactly one consumer. Description Incoming events are arriving at the place Load Balancer and are forwarded (pushed) to the Consumer by transition T1. For each Consumer, an own mode in transition T1 is implemented. All these modes have the same fire weight. The events are uniformly distributed among consumers. QPN Definition Places: Place Type Description Load Balancer S Receives inc. events and forwards them to the Consumer. Consumer i S Consumes incoming events. One place for each Consumer. Colors: Color Event Description Represents a published event. Transitions: Id Input Output FW Description T1 1 Event (Load Balancer) 1 Event (Consumer) 1 Forwards event to Consumer.
4.2. PERFORMANCE MODELING PATTERN 69 Pattern 10: Round-robin Load Balancer Load Balancer T1: Round Robin Consumer 1 Event Consumer 1 Load Balancer Event Consumer 2 Event ... ... ... Load Balancer T1 ... Consumer 2 Consumer n NextIsC1 NextIsC2 ... NextIsCn Consumer n Event Load Balancer NextIsC1 ... NextIsC2 Figure 4.19: Load Balancer - Round Robin Characteristics • Load balancing • Round-robin Example Incoming events are processed by a load balancer and afterwards distributed among event consumers in a round robin manner. Each event is forwarded to exactly one consumer. Description Incoming events are arriving at the place Load Balancer and forwarded to the Consumer by transition T1. For each Consumer exists an own mode in transition T1. Further, a token named NextIsC i is defined. i is the unique id of the consumer, e.g. for Consumer 1 the color name is NextIsC1. To implement a round robin behavior the load balancer needs to keep track which Consumer is next. We model this knowledge by storing a NextIsC i token in the Load Balancer. This token identifies the Consumer i who should receive the next Event. As illustrated in Figure 4.19, the modes of transition T1 takes into account, which consumer is next and update the state of the Load Balancer by replacing the NextIsC i token with a NextIsC i+1 token. For example, if an Event token and a NextIsC1 token are stored in the depository place of the load balancer, the corresponding mode of transition T1 is fired. The Event token is forwarded to Consumer 1 and the NextIsC1 token is replaced by a NextIsC2 token. To initialize the model we have to specify the consumer that should receive the first Event token. This is done by initializing the corresponding NextIsC i token.
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 31 and 32: 2.2. TECHNOLOGY PLATFORMS OF EVENT-
Page 33 and 34: 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 81: 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?