As an Open Source company we believe in giving credit where credit is due. The majority of the technical ideas in this post were not invented at Chrom

Designing a query execution engine#

submited by
Style Pass
2024-10-30 17:30:04

As an Open Source company we believe in giving credit where credit is due. The majority of the technical ideas in this post were not invented at Chroma, and we reference research and systems from which we have generously borrowed techniques and architecture.

Distributed Chroma is a multi-tenant system. Query and Compactor nodes serve queries and build indexes for multiple tenants. By leveraging multi-tenancy we can maximize utilization of nodes in our system, resulting in lower costs for our users. However, building with multi-tenancy in mind presents the challenge of how to optimally structure, dispatch, and schedule work such that resources are fairly used across all tenants.

This constraint led us to search for an execution model for Query and Compaction nodes. We needed an execution model that would allow us to:

Luckily, database researchers and practitioners have a well understood set of execution models to learn and borrow from. A common separation between these execution models is whether they are pull-based or push-based. Let’s consider a basic SQL query in order to explain the difference.

Leave a Comment