Performance Modeling and Benchmarking of Event-Based ... - DVS
Performance Modeling and Benchmarking of Event-Based ... - DVS
Performance Modeling and Benchmarking of Event-Based ... - DVS
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
4.2. PERFORMANCE MODELING PATTERN 71<br />
Pattern 11: Queuing Load Balancer<br />
Consumer 1<br />
...<br />
...<br />
...<br />
Load<br />
Balancer<br />
T1<br />
Consumer 2<br />
1‘Ready 1‘Ready<br />
1‘<strong>Event</strong> 1‘<strong>Event</strong><br />
...<br />
T2<br />
Consumer n<br />
T1: Pull <strong>Event</strong><br />
T2: Consumer is ready<br />
Consumer 1<br />
Ready<br />
Consumer 2<br />
Ready<br />
Consumer n<br />
Ready<br />
Load Balancer<br />
Consumer 1<br />
<strong>Event</strong><br />
Consumer 2<br />
<strong>Event</strong><br />
Consumer n<br />
<strong>Event</strong><br />
Consumer 1<br />
<strong>Event</strong><br />
Consumer 2<br />
<strong>Event</strong><br />
Consumer n<br />
<strong>Event</strong><br />
Consumer 1<br />
Ready<br />
Consumer 2<br />
Ready<br />
Consumer n<br />
Ready<br />
<strong>Event</strong><br />
Figure 4.20: Load Balancer - Pull<br />
Example<br />
Incoming events are stored at the load balancer, e.g., in a queue. If a consumer has free resources<br />
he pulls an event <strong>and</strong> processes it.<br />
Characteristics<br />
• Load Balancing<br />
• Resource controlled<br />
• Pull-based<br />
Description<br />
Patterns 9 & 10 model a Load Balancer, who pushes <strong>Event</strong>s directly after processing them to the<br />
Consumer. In this scenario the Load Balancer stores them after processing <strong>and</strong> the Consumer<br />
pulls <strong>Event</strong> tokens based on the availability <strong>of</strong> resources.