Database
Tessera: Fast Join-Aggregates over Skewed Sparse Relations in Database Engines
arXiv cs.DB0 views
arXiv:2610.40620v2 Announce Type: replace Abstract: Join-aggregate queries count or sum matching rows for each pair of values, often over skewed sparse relations in which a few values are frequent and most pairs of values never co-occur. Conventional execution plans materialize billions of intermediate join rows, taking minutes to tens of minutes per query. Recent matrix-based solutions reformulate these queries as matrix multiplication to reduce or avoid this materialization. However, they remain slow because they either store result cells for non-matching pairs or still materialize intermediate join rows for infrequent values. We present Tessera, a skew-aware join-aggregate operator for database engines that avoids both sources of overhead. Specifically, Tessera computes a sparse matrix product directly over the engine's rows, emits only nonzero cells as result rows, and prunes values that cannot meet the query's threshold before multiplication begins. It also offloads the dense block formed by pairs of the most frequent values to a CPU matrix accelerator when that block is dense enough. Experimental results show that Tessera is faster than the fastest existing system by 2.8x to 18.8x. In addition, Tessera outperforms DuckDB's execution plans by up to 1,802x.
Source:https://arxiv.org/abs/2610.40620PreviousRecommendation Systems for Exploratory Data TasksNextTowards Universal Tabular Embeddings: A Benchmark Across Data Tasks
Related posts
How to upgrade Postgres in Docker to 18, and be ready for 19: dump and restore or pg_upgrade --link
0dev.to Docker
Docker Compose: Run Your App and Its Dependencies Together
0dev.to Docker
Show HN: Vaire, Self-Hosting Postgres Through the One Glorious CLI
0Hacker News Show
Gabriele Bartolini: CloudNativePG reaches CNCF Incubation: another rung on the ladder
0Planet PostgreSQL
pandas chunks fixed my memory error, then quietly broke my averages
0dev.to
Postgres LISTEN/NOTIFY vs Redis Pub/Sub: Latency, Write Cost and Failure Cases, Tested
0dev.to Node