On the necessity of explicit cross-layer data formats in near-data processing systems

Abstract

Massive data transfers in modern data-intensive systems resulting from low data-locality and data-to-code system design hurt their performance and scalability. Near-Data processing (NDP) and a shift to code-to-data designs may represent a viable solution as packaging combinations of storage and compute elements on the same device has become feasible. The shift towards NDP system architectures calls for revision of established principles. Abstractions such as data formats and layouts typically spread multiple layers in traditional DBMS, the way they are processed is encapsulated within these layers of abstraction. The NDP-style processing requires an explicit definition of cross-layer data formats and accessors to ensure in-situ executions optimally utilizing the properties of the underlying NDP storage and compute elements. In this paper, we make the case for such data format definitions and investigate the performance benefits under RocksDB and the COSMOS hardware platform.

Near-data processing in database systems on native computational storage under HTAP workloads

“…It comprises information about DBobjects, their columns, types, sizes, or their physical representation. The on-device NDP infrastructure employs schema information to support data layout accessors for in-situ navigation, and format parsers for data interpretation [68,72]. We also introduce physical page pointers to reduce the overhead of large address mappings.…”