Key result
UDF outlining accelerates query performance up to ~299x versus conventional inlining.
Why the study?
Although UDF inlining replaces UDF calls with SQL subqueries, inlining the entire UDF often leads to sub-optimal query performance.
UDF outlining significantly improves query performance compared to conventional inlining by hiding pieces of a UDF from the optimizer.
Although user-defined functions (UDFs) are a popular way to augment SQL's declarative approach with procedural code, the mismatch between programming paradigms creates a fundamental optimization challenge. UDF inlining automatically removes all UDF calls by replacing them with equivalent SQL subqueries. Although inlining leaves queries entirely in SQL (resulting in large performance gains), we observe that inlining the entire UDF often leads to sub-optimal performance. A better approach is to analyze the UDF, deconstruct it into smaller pieces, and inline only the pieces that help query optimization. To achieve this, we propose UDF outlining, a technique to intentionally hide pieces of a UDF from the optimizer, resulting in simpler UDFs and significantly faster query plans. Our implementation (PRISM) demonstrates that UDF outlining improves performance over conventional inlining (on average 1.29× speedup for DuckDB and 298.73× for SQL Server) through a combination of more effective unnesting, improved data skipping, and by avoiding unnecessary joins.
No takes yet. Share an insight, caveat, or question.
Arch et al. (2024) studied this question. UDF outlining (PRISM) vs. conventional inlining was evaluated on query performance speedup (1.29× speedup for DuckDB and 298.73× for SQL Server). UDF outlining improved query performance over conventional inlining, achieving an average 1.29× speedup for DuckDB and 298.73× for SQL Server.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: