20.01.2015 Views

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

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

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

SHOW MORE
SHOW LESS

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 6<br />

<strong>Performance</strong> <strong>Modeling</strong> <strong>of</strong> EBS -<br />

Case Studies<br />

In this chapter we present two case studies in which we apply our approach for workload characterization<br />

<strong>and</strong> performance modeling <strong>of</strong> event-based systems introduced in Chapter 4. In the first<br />

case study we use the SIENA [40] publish/subscribe system with a basic workload comprising a<br />

single message type. In the second more complex case study we model a realistic state-<strong>of</strong>-the-art<br />

event-driven system on a leading commercial middleware platform including all system layers.<br />

A detailed system model is built in a step-by-step fashion <strong>and</strong> then used to predict the system<br />

performance under various workload <strong>and</strong> configuration scenarios. In both case studies, we show<br />

how QPN models can be exploited for performance analysis <strong>and</strong> capacity planning in the s<strong>of</strong>tware<br />

engineering process. The results demonstrate the effectiveness, practicality <strong>and</strong> accuracy<br />

<strong>of</strong> the proposed modeling <strong>and</strong> prediction approach, which provides a powerful tool for ensuring<br />

that systems are designed <strong>and</strong> sized to meet their QoS requirements. Furthermore, we apply<br />

our performance modeling patterns (Section 4.2) <strong>and</strong> make use <strong>of</strong> QPN extensions (Section 4.3)<br />

in the second case study.<br />

6.1 DEBS Case Study<br />

6.1.1 Scenario<br />

We consider a scenario in which DEBS is used to manage the interactions among participants<br />

in a supermarket supply chain [202]. The participants involved are the supermarket company,<br />

its stores, its distribution centers <strong>and</strong> its suppliers. Since most <strong>of</strong> the interactions in the supply<br />

chain are asynchronous in nature, they can be implemented using DEBS. Some examples <strong>of</strong><br />

services that can be h<strong>and</strong>led by the system are supermarket order <strong>and</strong> shipment h<strong>and</strong>ling,<br />

inventory management in supermarkets <strong>and</strong> distribution centers, automated tracking <strong>of</strong> goods<br />

as they move through the supply chain <strong>and</strong> dissemination <strong>of</strong> new product announcements,<br />

price updates, special <strong>of</strong>fers <strong>and</strong> discount information from the company headquarters to the<br />

supermarkets. Here we consider a simplified version <strong>of</strong> the SPECjms2007 scenario (see Section<br />

5.1), in which the dissemination <strong>of</strong> requests for quotes are sent when goods in a distribution center<br />

are depleted <strong>and</strong> an order has to be placed to refill stock. A request for quote is published as<br />

an event in the system <strong>and</strong> it is automatically delivered to all suppliers that <strong>of</strong>fer the respective<br />

types <strong>of</strong> goods. It is assumed that suppliers have subscribed to all events belonging to the<br />

product groups/categories they sell.<br />

119

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!