Main Page

From BiCEP

Jump to: navigation, search
Line 1: Line 1:
-
<big>'''Project BiCEP'''</big>
 
-
BiCEP is a project started in the Systems and Software Engineering Group at the University of Coimbra. The goal of the project is to produce benchmarks for [http://www.complexevents.com:Complex Event Processing] systems (CEP).
 
Line 8: Line 6:
*'''NEW paper: ''' Rafael Marmelo, Pedro Bizarro, and Paulo Marques. 9ticks – The Web as a Stream ([[Media:9ticks_dait2009.pdf‎|pdf]]). In the First International Workshop on Database Architectures for the Internet of Things (DAIT 2009). Extended version ([[Media:9ticks_iete2009.pdf|pdf]]) also published on the 2009 September/October issue of IETE Technical Review journal. (paper and details coming soon)
*'''NEW paper: ''' Rafael Marmelo, Pedro Bizarro, and Paulo Marques. 9ticks – The Web as a Stream ([[Media:9ticks_dait2009.pdf‎|pdf]]). In the First International Workshop on Database Architectures for the Internet of Things (DAIT 2009). Extended version ([[Media:9ticks_iete2009.pdf|pdf]]) also published on the 2009 September/October issue of IETE Technical Review journal. (paper and details coming soon)
-
----
+
== Description ==
-
The goal of project BiCEP is to study the performance and develop benchmarks for Complex Event Processing systems. CEP metrics should include the following metrics (some obvious, others not quite):
+
BiCEP is a project started in the Systems and Software Engineering Group at the University of Coimbra. The goal of the project is to produce benchmarks for [http://www.complexevents.com:Complex Event Processing] systems (CEP). CEP metrics should include the following metrics (some obvious, others not quite):
* '''Sustainable throughput''': the steady-state number of events per unit of time that a (warmed-up) CEP engine can process while performing query processing. Even within the same system, sustainable throughput can vary widely depending on the amount of work to be done during query processing.
* '''Sustainable throughput''': the steady-state number of events per unit of time that a (warmed-up) CEP engine can process while performing query processing. Even within the same system, sustainable throughput can vary widely depending on the amount of work to be done during query processing.
* '''Response time''': the time since the last event of some event pattern is fed into the system until the system notifies the event pattern detection.
* '''Response time''': the time since the last event of some event pattern is fed into the system until the system notifies the event pattern detection.

Revision as of 23:38, 20 July 2009

Personal tools