Cookie Notice
This site uses cookies for performance, analytics, personalization and advertising purposes.
For more information about how we use cookies please see our Cookie Policy.
Manage Consent Preferences
These cookies are essential in order to enable you to move around the website and use its features, such as accessing secure areas of the website.
These are analytics cookies that allow us to collect information about how visitors use a website, for instance which pages visitors go to most often, and if they get error messages from web pages. This helps us to improve the way the website works and allows us to test different ideas on the site.
These cookies allow our website to properly function and in particular will allow you to use its more personal features.
These cookies are used by third parties to build a profile of your interests and show you relevant adverts on other sites. You should check the relevant third party website for more information and how to opt out, as described below.
They are both designed for high-performance SQL queries on large datasets. Trino and Presto are often used in big data and analytics applications to query and analyze data stored in various data sources, including Hadoop Distributed File System (HDFS), relational databases, cloud storage, and more.
While they share similarities, there are differences between Trino and Presto, such as the development community, features, and performance optimizations. It’s important to consider your specific use case and requirements when choosing between these query engines to determine which one is the best fit for your needs.
Trino is the new name for PrestoSQL
Presto is the name of the query engine originally developed by Martin Traverso, Dain Sundstrom, David Phillips, and Eric Hwang at Facebook in 2012. Hive map reduce jobs were taking too long at Facebook’s scale, and Presto was created as a massively-parallel processing query engine that could turn 12+ hour SQL queries into queries that only took minutes or seconds.
Over the next several years, Presto expanded to cover a wide range of data sources, serving any database, data warehouse, or data lake, and able to easily integrate with BI tools. Being built as a SQL engine meant that data scientists and analysts using Presto could tap into their existing skills.
In 2018, Martin, Dain, and David left Facebook to create a fork of Presto which could better serve the open source community instead of just Facebook. The fork was initially called PrestoSQL, but they later rebranded to Trino in 2020.
While Presto was primarily developed at Facebook and Uber to serve hyper-scale internet companies, Trino was expanded on to serve a much broader variety of customers and use cases, while still including those hyper-scale web companies. Companies like Amazon, LinkedIn, Lyft, Netflix, Salesforce, Condé Nast, Goldman Sachs, and FINRA use Trino, among thousands of others.
Both Presto and Trino feature the same core ANSI SQL-compliant query engine. Their architecture is identical, and the two engines can be used in place of each other for most lightweight analytics workloads. However, there are several key differences and features unique to each query engine that are worth knowing about.
We’re not going to mince words. In our opinion, Trino is the superior query engine. Since the two projects were forked, Trino’s development has been going at roughly thrice the pace of Presto’s, and it shows. It runs faster and serves a much wider variety of use cases. If your existing tech stack heavily relies on Spark and Hive for all things data, it may make sense to use Presto. For all other situations, Trino is the better, more versatile, more powerful option.
A few sprinkles on top: if you are using Hive, Trino has a built-in procedure to migrate your Hive tables to Apache Iceberg, allowing you to easily modernize your data stack and reap the performance and cost benefits. Some users who’ve already gone through with migrating have seen certain queries execute 95% faster.
Creator of Presto, Creator of Trino, Co-Founder of the Trino Software Foundation, and CTO at Starburst. Prior to Starburst, Martin worked as a Software Engineer at Facebook, and a Software Architect at Proofpoint and Ning.
Creator of Presto, Creator of Trino, Co-Founder of the Trino Software Foundation, and CTO at Starburst. Prior to Starburst, Dain was a Software Engineer at Facebook, a Software Architect at Proofpoint, founded the Apache Geronimo project, and was one of the original JBoss authors.
Creator of Presto, Creator of Trino, Co-Founder of the Trino Software Foundation, and CTO at Starburst. Prior to Starburst, David was a Software Engineer at Facebook, and held senior engineering positions at Proofpoint, Ning and Adknowledge.
Up to $500 in usage credits included
© Starburst Data, Inc. Starburst and Starburst Data are registered trademarks of Starburst Data, Inc. All rights reserved. Presto®, the Presto logo, Delta Lake, and the Delta Lake logo are trademarks of LF Projects, LLC
Up to $500 in usage credits included