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.
Chapter 1<br />
Introduction<br />
1.1 Motivation<br />
<strong>Event</strong>-based systems (EBS) have been gaining attention in many domains <strong>of</strong> industry. With<br />
the advent <strong>of</strong> ambient intelligence <strong>and</strong> ubiquitous computing, many new applications <strong>of</strong> EBS<br />
have been proposed [101], for example, in the areas <strong>of</strong> transport information monitoring [15,<br />
206], event-driven supply chain management [33, 1, 196], ubiquitous (wireless) sensor environments<br />
[2, 30, 179], environmental monitoring, ambient assisted living, <strong>and</strong> location-based<br />
services [59, 35, 102, 100]. Many <strong>of</strong> these novel event-based applications are highly distributed<br />
<strong>and</strong> data intensive <strong>and</strong> hence pose some serious performance <strong>and</strong> scalability challenges. With<br />
the increasing popularity <strong>of</strong> EBS <strong>and</strong> their gradual adoption in mission critical areas, performance<br />
issues are becoming a major concern. The performance <strong>and</strong> scalability <strong>of</strong> event-based<br />
middleware (used to process real-time event data) are <strong>of</strong> crucial importance for the successful<br />
adoption <strong>of</strong> such applications in the industry, <strong>and</strong> methodologies are needed to guarantee an<br />
adequate quality-<strong>of</strong>-service (QoS) level.<br />
As a consequence, EBS have to be subjected to a rigorous performance analysis at all stages<br />
<strong>of</strong> an application’s life cycle. To meet QoS requirements, techniques for predicting system<br />
performance as a function <strong>of</strong> configuration <strong>and</strong> workload are needed. Common performance<br />
metrics <strong>of</strong> interest are, for example, expected event notification latency as well as utilization <strong>and</strong><br />
message throughput <strong>of</strong> the various system components (e.g., event brokers, network links). Since<br />
the components <strong>of</strong> EBS are loosely coupled <strong>and</strong> communicate asynchronously, the underst<strong>and</strong>ing<br />
<strong>of</strong> these metrics may differ from traditional performance engineering. However, obtaining such<br />
information is essential in order to determine the optimal system topology, configuration, <strong>and</strong><br />
capacity for providing adequate QoS to applications at a reasonable cost. Moreover, given<br />
the dynamics <strong>of</strong> most EBS applications, it is important that the performance <strong>of</strong> the system<br />
is continuously monitored <strong>and</strong> analyzed during operation to help anticipate changes in the<br />
workload <strong>and</strong> take corrective actions to ensure that QoS requirements are satisfied.<br />
The goal <strong>of</strong> this thesis is to develop novel approaches to analyze <strong>and</strong> predict the behavior <strong>of</strong><br />
EBS <strong>and</strong> their performance <strong>and</strong> scalability under load. To achieve this, we focus on workload<br />
characterization, benchmarking <strong>and</strong> performance modeling.<br />
1.2 Problem Statement<br />
EBS are <strong>of</strong>ten used in business critical environments <strong>and</strong> thus their reliability is crucial for<br />
the whole IT infrastructure. A certain QoS level has to be ensured. Since EBS are loosely<br />
coupled, highly distributed, data intensive <strong>and</strong> <strong>of</strong>ten heterogeneous systems, this is a very challenging<br />
task. The dynamics <strong>of</strong> most EBS applications <strong>and</strong> their underlying middleware makes<br />
1