On-Demand Recordings from PrestoCon’s, Webinars, Meetups, and more
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.
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.
You use multiple tools for databases, for example Azure Data Studio for SQLServer access, Toad or SQLDeveloper for Oracle access, MySQLWorkbench for MySQL databases. Imagine we have one tool and we can query any database, bring any table from any catalog to a single canvas! Now you join, the underlying PrestoDB compatible query is generated. Click a button, you get the profiled data, including distributions and correlations. An amazing tool in action.