Skip to content
Review Open access

An Empirical Evaluation of SystemC Transaction Data Storage Formats

2026 · International Conference on Simulation and Modeling Methodologies, Technologies and Applications · pp. 27-38 · 0 citations · 15 references
Computer Science

TL;DR

The findings demonstrate that modern analytical storage techniques can significantly improve SystemC transaction tracing workflows and show that storage layout is a first-order determinant of footprint and query performance at scale.

Abstract

: SystemC transaction-level modeling (TLM) is widely used for system integration, virtual platform simulation, and early software bring-up, yet storage and analysis of TLM traces remains unstandardized and largely driven by convenience or legacy tooling. This paper presents a comparative empirical evaluation of storage formats for SystemC TLM-2.0 transaction traces and, to our knowledge, the first peer-reviewed evaluation of columnar (Apache Parquet) and array-oriented (Zarr) formats in this context. We evaluate CSV, SQLite, Parquet, and Zarr across workloads ranging from deterministic microbenchmarks to full-system Linux boot, measuring write-time overhead, storage footprint, and post-simulation query performance. Results show that storage layout is a first-order determinant of footprint and query performance at scale. Parquet achieves order-of-magnitude reductions in trace size and substantial speedups for scan-heavy and temporal aggregation queries, while SQLite consistently outperforms alternatives for selective, record-oriented access. No single format dominates across all workloads; however, the findings demonstrate that modern analytical storage techniques can significantly improve SystemC transaction tracing workflows.

Read PDF

Similar papers

Conference Aug 2026

Assessing the Impact of CQRS Pattern Implementation on Query Latency in .NET Blazor CRUD Systems

Modern web applications are increasingly reliant on Object-Relational Mapper (ORM) frameworks to bridge the gap between high-level application logic and relational databases. However, in standard Create, Read, Update, and Delete (CRUD) architectures, the use of a unified data model often leads to significant performanc...

Justin Evan Surya, Kenny Jingga · 0 citations
Open access 2023

Polyglot Persistence and Enterprise Data Migration: Architectures, Consistency, and Practice

Developments point toward enterprise data platforms that treat migration and persistence design as a continuum rather than separate disciplines: architectural choices made during migration planning directly determine how well the resulting system supports polyglot workloads, real-time analytics, and regulatory-grade in...

Yasmeen Syed · 0 citations
Open access Sep 2026

Analyzing CRUD Performance and Data Integrity Trade-offs in MariaDB: The Impact of Indexes, Foreign Keys, and Referential Actions

Data integrity in RDBMS frequently raises concerns regarding computational efficiency, particularly when handling large-scale datasets. This study analyzes the trade-off between execution time and storage overhead in MariaDB (InnoDB storage engine) by evaluating different configurations of indexing, foreign key constra...

Y. Sudiyono, Jaka Suwita, W. Winanti · 0 citations

T 𝒆𝒙𝑩𝒆𝒏𝒄𝒉 : A Unified Benchmarking Suite for Shifting Workloads

A unified key-value benchmarking suite that enables benchmarking key-value stores against dynamically shifting and production-like workloads and comparing their performance side by side and allows users to benchmark multiple databases and perform an apples-to-apples comparison under the same workload readily within a s...

Abhishek Chanda, Shubham Kaushik, A. Lavrov et al. · 0 citations

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.