Benchmarks

From BiCEP

Jump to: navigation, search
Line 1: Line 1:
-
 
== ''Pairs'' ==
== ''Pairs'' ==
The scenario for ''Pairs'' is an investment firm where a number of analysts interact with an enterprise trading system responsible for automating and optimizing the execution of orders in stock markets. Users of the system pose trading strategies which are continuously matched against live stock market data. The task of an event processing system implementing ''Pairs'' is thus to process this tick stream and compute, for each running strategy, a set of indicators, signalizing whenever those reveal an opportunity to capitalize on market inefficiencies.  
The scenario for ''Pairs'' is an investment firm where a number of analysts interact with an enterprise trading system responsible for automating and optimizing the execution of orders in stock markets. Users of the system pose trading strategies which are continuously matched against live stock market data. The task of an event processing system implementing ''Pairs'' is thus to process this tick stream and compute, for each running strategy, a set of indicators, signalizing whenever those reveal an opportunity to capitalize on market inefficiencies.  
Line 10: Line 9:
* Changing load conditions.
* Changing load conditions.
-
The most updated specification of ''Pairs'' (revision 0.2) can be found [http://bicep.dei.uc.pt/images/b/ba/Pairs_Benchmark_%28rev._0.2%29.pdf here]. The benchmark kit, required to run ''Pairs'', can be donwloaded from the [http://bicep.dei.uc.pt/index.php/Tools Tools] section.
+
The benchmark should be implemented as illustrated in the figure below:
 +
 
 +
[[File:Benchmark Flow.png]]
 +
 
 +
Initially, the user specifies a couple of workload parameters or, alternatively, uses the standard benchmark configuration to create a test setup (1). Then, a data generator application generates data and auxiliary files (2), which are used afterwards by a query generator to produce the strategies that compose the benchmark workload (3). The output of the query generator is then parsed by a vendor-specific translator, which converts the workload, initially represented in a neutral format (e.g., xml file), into the query language used by the SUT (4). After loading the query/rule set into the SUT (5), the user starts a performance run (6). During the run, the benchmark driver (FINCoS) loads the generated data file and submits the events on it to the SUT (7), which in turn returns the corresponding results to the framework (8). After test completion, a validator verifies the correctness of the answers produced by the SUT (9).
 +
 
 +
All the aforementioned tools are written in Java and are available for download in the [http://bicep.dei.uc.pt/index.php/Tools Tools] section. Further details about the ''Pairs'' benchmark can be found on its [http://bicep.dei.uc.pt/images/b/ba/Pairs_Benchmark_%28rev._0.2%29.pdf specification] (currently on revision 0.2).

Revision as of 19:27, 24 January 2013

Personal tools