Timo Kersten

ORCID: 0000-0002-0004-9686
Publications
Citations
Views
---
Saved
---
About
Contact & Profiles
Research Areas
  • Data Management and Algorithms
  • Advanced Database Systems and Queries
  • Cloud Computing and Resource Management
  • Scientific Computing and Data Management
  • Parallel Computing and Optimization Techniques
  • Graph Theory and Algorithms
  • Distributed systems and fault tolerance
  • Embedded Systems Design Techniques
  • Distributed and Parallel Computing Systems
  • Advanced Graph Neural Networks
  • Software Testing and Debugging Techniques

Technical University of Munich
2017-2021

The query engines of most modern database systems are either based on vectorization or data-centric code generation. These two state-of-the-art processing paradigms fundamentally different in terms system structure and execution code. Both were used to build fast systems. However, until today it is not clear which paradigm yields faster execution, as many implementation-specific choices obstruct a direct comparison architectures. In this paper, we experimentally compare the models by...

10.5555/3275366.3284966 article EN Very Large Data Bases 2018-09-01

The query engines of most modern database systems are either based on vectorization or data-centric code generation. These two state-of-the-art processing paradigms fundamentally different in terms system structure and execution code. Both were used to build fast systems. However, until today it is not clear which paradigm yields faster execution, as many implementation-specific choices obstruct a direct comparison architectures. In this paper, we experimentally compare the models by...

10.14778/3275366.3284966 article EN Proceedings of the VLDB Endowment 2018-09-01

Abstract Although compiling queries to efficient machine code has become a common approach for query execution, number of newly created database system projects still refrain from using compilation. It is sometimes claimed that the intricacies generation make compilation-based engines too complex. Also, major barrier adoption, especially interactive ad hoc queries, long compilation time. In this paper, we examine all stages execution and show how reduce overhead. We incorporate lessons...

10.1007/s00778-020-00643-4 article EN cc-by The VLDB Journal 2021-06-02

The query engines of most modern database systems are either based on vectorization or data-centric code generation. These two state-of-the-art processing paradigms fundamentally different in terms system structure and execution code. Both were used to build fast systems. However, until today it is not clear which paradigm yields faster execution, as many implementation-specific choices obstruct a direct comparison architectures. In this paper, we experimentally compare the models by...

10.14778/3275366.3275370 article EN Proceedings of the VLDB Endowment 2018-09-01

Analytical graph algorithms commonly compute metrics for a at one point in time. In practice it is often also of interest how change over time, e.g., to find trends. For this purpose, must be executed multiple snapshots. We present Single Algorithm Multiple Snapshots (SAMS) , novel approach execute concurrently SAMS automatically transforms leverage similarities between the analyzed The automatic transformation interleaves algorithm executions on snapshots, synergistically shares their...

10.14778/3090163.3090166 article EN Proceedings of the VLDB Endowment 2017-04-01

Dataflow graphs are a popular abstraction for describing computation, used in many systems high-level optimization. For execution, dataflow lowered and optimized through layers of program representations down to machine instructions. Unfortunately, performance profiling such is cumbersome, as today's profilers present results merely at instruction function granularity. This obfuscates the connection between profiles constructs, operators pipelines, making interpretation an exercise puzzling...

10.1145/3447786.3456254 article EN 2021-04-21

Compilation-based query engines generate and compile code at runtime, which is then run to get the result. In this process there are two levels of source involved: The generator itself that generated runtime. This can make debugging quite indirect, as a fault in was caused by an error generator. To find error, we have look both, it. Current technology not equipped handle situation. For example, GNU's gdb only offers facilities inspect one line, but multiple levels. Also, current debuggers...

10.1145/3395032.3395321 article EN 2020-05-25
Coming Soon ...