Abstract

To cope with the increased complexity of systems, models are used to capture what is considered the essence of a system. Such models are typically represented as a graph, which is queried to gain insight into the modelled system. Often, the results of these queries need to be adjusted according to updated requirements and are therefore a subject of maintenance activities. It is thus necessary to support writing model queries with adequate languages. However, in order to stay meaningful, the analysis results need to be refreshed as soon as the underlying models change. Therefore, a good execution speed is mandatory in order to cope with frequent model changes. In this paper, we propose a benchmark to assess model query technologies in the presence of model change sequences in the domain of social media. We present solutions to this benchmark in a variety of 11 different tools and compare them with respect to explicitness of incrementalization, asymptotic complexity and performance.

Highlights

  • Models are a highly valuable asset in any engineering process as they capture the knowledge of a system in a formal abstraction

  • 4 School of Informatics, University of Leicester, Leicester, UK 5 IMT Atlantique, LS2N (UMR CNRS 6004), Nantes, France 6 DIRO, Université de Montréal, Montreal, Canada 7 ERIS, ESEO-TECH, Angers, France 8 Department of Telecommunications and Media Informatics, Budapest University of Technology and Economics, Budapest, Hungary 9 Department of Measurement and Information Systems, Budapest University of Technology and Economics, Budapest, Hungary 10 CWI, Amsterdam, The Netherlands propagate these changes to the analysis results incrementally, i.e. only recalculate those parts of the analysis results that are affected by a given change

  • Does the tool fit into my technology space? Is it useful to rely on the incrementalization of a tool or is it better—at least performance-wise—to implement change propagation explicitly? How long does it take to recover from an application crash? How much development effort will be necessary to implement change propagation? How does it scale? Can I speed it up by adding more CPU cores? Is the tool extensible or can it happen that my analysis is not supported at some point

Read more

Summary

Introduction

Models are a highly valuable asset in any engineering process as they capture the knowledge of a system in a formal abstraction. Is the tool extensible or can it happen that my analysis is not supported at some point?1 To aid this comparison and assess how current modelling technologies are capable of offering a concise and understandable language for model analysis, yet still offer a good performance in the presence of frequent model changes, we propose the “Social Media” benchmark. In this benchmark, two queries should be formulated that analyse a model of a social media network.

The social media benchmark
Metamodel and change sequences
Queries
Query 1
Query 2
Change sequences
Updates
Solutions
Common solution approaches
Reference solution
Tool description
Transactions and parallelism
3.10.2 Query 1
3.10.1 Tool description
3.11.1 Tool description
3.11.2 Query 1
3.11.3 Query 2
3.12.1 Tool description
3.12.2 Query 1
3.12.3 Query 2
3.13 PostgreSQL incremental
3.13.1 Tool description
The initial step consists of two substeps:
The interim result maintenance is again split into two substeps:
3.13.3 Query 2
25 FROM comments c
3.14.1 Tool description
3.14.2 Query 1
3.15 GraphBLAS incremental
3.15.1 Tool description
3.15.2 Query 1
3.15.3 Query 2
3.16.1 Tool description
3.16.2 Query 1
3.16.3 Query 2
Classification
Declarative query language
Data model
Explicitness of incrementalization
Persistence
Parallelism
Asymptotic complexity to propagate changes
JastAdd
PostgreSQL batch
PostgreSQL incremental
Neo4j incremental
GraphBLAS
4.6.10 Summary
Performance evaluation
Input models
Benchmark framework
Benchmark environment
Analysis
Batch solutions
Implicit incremental solutions
Explicit incremental solutions
Selected incremental tools
Internal threats to validity
External threats to validity
Comparative studies
Incrementality
Conclusion
Future work
22 UPDATE comments c
11 DELETE l
15 YIELD node AS newComp
Comparison of solution variants

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.