atlas

Research map / Large language models / Agents, code and math

Column-Oriented Datalog on the GPU

AAAI 2025 · Large language models › Agents, code and math · approach: Code generation benchmarks · 1 citations (OpenAlex)

Read the paperCheck your idea against 108,967 papers

AI-extracted summary. Written by AI from the paper's full text. Numbers and claims can be wrong or missing context, so check the paper before you cite or build on it.

Presents FVlog, a CUDA-based column-oriented (decomposed storage model) Datalog runtime for GPUs with hybrid sorted-index/hashmap indexing and eager merging, reporting large speedups over CPU column-oriented engines and GPU row-oriented engines.

Problem

Whether column-oriented or row-oriented tuple storage is more effective for Datalog evaluation on modern datacenter GPUs, since prior column-oriented Datalog engines were CPU-only and GPU Datalog engines used row layouts.

Approach

Stores each relation as decomposed columns with surrogate IDs, a raw data array, sorted indices and a run-length-encoded unique hashmap per column; joins return only matched surrogate columns, deduplication uses a GPU-friendly hash-plus-overlap check instead of tries, and delta tuples are eagerly merged into the full relation for memory continuity.

Key results

Measured effects reported in the paper

What was changedWhereMeasuredEffect
Column-oriented GPU layout (FVlog) vs CPU column-oriented engines (VLog, Nemo)FVlog on H100 · Same Generation query, SparseSuite graphsrunning time (s): at least 150x faster than VLog and Nemo in all cases; 584x vs VLog on vsp_finanHelped
Column-oriented GPU layout vs row-oriented GPU engines (GDlog, GPUJoin)FVlog on H100 · Transitive closure, six graphsrunning time (s): on average 2.5x faster than GDlog and 5.7x faster than GPUJoinHelped
GPU execution vs CPU execution of same FVlog data structures (ablation)FVlog · LUBM TGD reasoningrunning time (s): GPU at least 15x faster than CPU versionHelped
Eagerly merging delta into full relation and using uncompressed raw data (vs VLog-style on-demand concatenation)FVlog · Transitive closure / SGrunning time (s)No clear effect
Hybrid indexing (sorted indices plus unique hashmap) vs pure hashmap indexing (GPUJoin)Datalog joins on GPU · Transitive closure benchmarksrunning time (s): GPUJoin 5.7x slower on averageHelped
Paper's claim that CPU variant speedup vs Nemo/VLog reflects data structures (ablation)FVlog CPU variant · LUBM 01Krunning time (s): CPU FVlog ~9.6x faster than Nemo/VLog on largest dataset; paper attributes about half of gain to data structuresMixed

Surprising findings

Limitations

Experimental setup

Datasets: SuiteSparse graphs LUBM (ChaseBench)

Benchmarks: Same Generation query on SuiteSparse graphs Transitive closure on SuiteSparse graphs LUBM TGD reasoning (ChaseBench)

Metrics: running time (seconds) speedup

Baselines: VLog Nemo Souffle RDFox GPUJoin GDlog

Builds on: VLog semi-naive evaluation GPUJoin Souffle Leapfrog Triejoin

Closest papers by meaning

Writing a paper in this area? scime draft is a free LaTeX editor with AI included, real-time co-authors and a check of your references and venue rules before you submit. It also imports OpenAI Prism projects.

Open scime draft

Get the next scime Dispatch and a monthly field update

Free. We send a confirmation link first; every email has a one-click unsubscribe. Privacy