Seven commandments for benchmarking semantic flow processing systems

Thomas Scharrenbach, Jacopo Urbani, Alessandro Margara, Emanuele Della Valle, Abraham Bernstein

Research output: Chapter in Book / Report / Conference proceedingConference contributionAcademicpeer-review

Abstract

Over the last few years, the processing of dynamic data has gained increasing attention in the Semantic Web community. This led to the development of several stream reasoning systems that enable on-the-fly processing of semantically annotated data that changes over time. Due to their streaming nature, analyzing such systems is extremely difficult. Currently, their evaluation is conducted under heterogeneous scenarios, hampering their comparison and an understanding of their benefits and limitations. In this paper, we strive for a better understanding of the key challenges that these systems must face and define a generic methodology to evaluate their performance. Specifically, we identify three Key Performance Indicators and seven commandments that specify how to design the stress tests for system evaluation.

Original languageEnglish
Title of host publicationThe Semantic Web
Subtitle of host publicationSemantics and Big Data - 10th International Conference, ESWC 2013, Proceedings
Pages305-319
Number of pages15
DOIs
Publication statusPublished - 9 Oct 2013
Event10th International Conference on The Semantic Web: Semantics and Big Data, ESWC 2013 - Montpellier, France
Duration: 26 May 201330 May 2013

Publication series

NameLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
Volume7882 LNCS
ISSN (Print)0302-9743
ISSN (Electronic)1611-3349

Conference

Conference10th International Conference on The Semantic Web: Semantics and Big Data, ESWC 2013
Country/TerritoryFrance
CityMontpellier
Period26/05/1330/05/13

Fingerprint

Dive into the research topics of 'Seven commandments for benchmarking semantic flow processing systems'. Together they form a unique fingerprint.

Cite this