Keynote: Presto – Swiss Army Knife for the Lakehouse – Tim Meehan
Presto has long been known for its ability to bridge together multiple sources of data using a single consistent language. Learn about the future direction and initiatives that will make Presto even more convenient, reliable and efficient for the Lakehouse.
The Past, Present, and Future of Presto – Philip Bell, Meta
PrestoDB recently underwent major architectural updates as the Presto Foundation grows membership and is looking to vastly grow the number of new commits and forks. Achieving this desired end state required successful refactoring and improving of Presto’s already impressive speed, efficiency, reliability, and extensibility. Establishing PrestoDB as a premier Open Source project required a major commitment of time and resources from Meta to ensure the community can benefit from this project for years to come, as well as positioning PrestoDB to evolve beyond what Meta alone could create. Members of the Presto Foundation need more of you to be involved in this major evolution in Presto’s history and core components, and bring your own inventive ideas to the mix.
Disaggregated Coordinator Production Rollout – Swapnil Tailor, Meta
We would like to talk about disaggregated coordinator production rollout with some stats. Also we can inform community about changes needed to support deployment of disaggregated coordinator.
Presto, Today & Beyond – Dipti Borkar, David Simmen, Girish Baliga & Biswapesh Chattopadhyay
In this PrestoCon talk, team of community experts share Presto evolution, Today & Beyond
Disaggregated Coordinator – Swapnil Tailor, Facebook
In the existing Presto architecture, single coordinator has become a bottleneck in a number of ways for cluster scalability. – With an increasing number of workers, the coordinator has the potential of slow down due to a high number of tasks. – In high QPS use cases, we have found workers can become starved of splits by excessive CPU being spend on task updates in coordinator. – Also with single coordinator, we have an upper limit on the worker pool because of above-mentioned reasons. To overcome with this challenges, we are coming up with a new architecture which supports multiple coordinators in a single cluster.