<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Join-Order on Kent Yao</title>
    <link>https://yaooqinn.github.io/tags/join-order/</link>
    <description>Recent content in Join-Order on Kent Yao</description>
    <generator>Hugo -- 0.157.0</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 25 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://yaooqinn.github.io/tags/join-order/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>LLMs for Join Order: An Apache Spark Perspective on the Three-Tier Ladder</title>
      <link>https://yaooqinn.github.io/posts/spark/llm-for-join-order-an-apache-spark-perspective/</link>
      <pubDate>Mon, 25 May 2026 00:00:00 +0000</pubDate>
      <guid>https://yaooqinn.github.io/posts/spark/llm-for-join-order-an-apache-spark-perspective/</guid>
      <description>Databricks and UPenn put an LLM agent to work as an offline join-order tuner and got P90 latency down 41% / geomean 1.288× speedup on JOB&amp;rsquo;s 113 queries — beating even perfect cardinality estimates. From the trenches of an open-source query engine, here is what that result does and does not prove.</description>
    </item>
  </channel>
</rss>
