Clarification on Query Optimizer Techniques from Trino Docs in Starburst Enterprise

Hi Starburst Community,

I have been studying the Trino documentation on query optimization, including techniques such as table statistics, cost in EXPLAIN, cost-based optimizations, pushdown, and adaptive plan optimizations (links below):

https://trino.io/docs/current/optimizer.html#

From watching the query plan analysis series by Mr. Lester Martin , my understanding is that all these optimization techniques work by default in Starburst Enterprise, since it is built on Trino.

Could you please confirm if this understanding is correct? Are these query optimizer features fully supported and enabled by default in Starburst Enterprise, or are there differences or additional configurations needed?

Thanks for clarifying!
Thara

100% correct. Starburst Enterprise is build on top of Trino so all that magical goodness of the CBO is also in Starburst Enterprise. Additionally, we have some performance improvements that we add from time to time. We either put those directly into Trino or sometimes we put them in our build first for a while to stabilize everything (and offer some differentiation) before ultimately/usually bringing them back into the Trino codebase.

1 Like