I have been trying to understand the limitations of BigQuery based on how it works under the hood, but it's hard for me to find an answer to the question in the title: Can BigQuery queries get assigned to a different root nodes?

I currently work with Redshift where there is only one cluster with one leader node. Everything goes through and is put together by the leader node. If the leader node does not have enough compute or storage, that means lower concurrency capabilities. Leader node is a bottleneck.

What I am trying to understand is, do we have a similar problem in BigQuery? I know we have a root node akin to the leader node in Redshift when a query is run. See picture below:

enter image description here

Google claims you can practically never run out of resources, which implies that BigQuery doesn't have the same issue as Redshift, but there is no clear explanation. Can the Dremel node tree depicted above be spun up multiple times based on how much compute you require? Could the root node be a bottleneck?


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.