Using Count’s DuckDB database alongside your own is a powerful way to unlock the freedom to do extensive analysis on your data, without worrying about the query load on your database. There are several ways to use this:
DuckDB in the browser |
|
| Switching database cells over to local cells that make use of memory in the browser. The benefit of this is that queries run really fast in the canvas, but the limitation is that the memory limit of this is about 120mb so you may need to aggregate your data into smaller chunks before switching to local.
|
DuckDB on the server |
|
| You can now hold up to 32GB (depending on which Plan you are on) in Count's local DuckDB database on the server, which means you can have even less initial database cells, and switch over to local cells sooner.
|
DuckDB in Count Metrics |
|
| In Count Metrics, our semantic layer, caching is available at a workspace level. This means you can cache query results and reuse these across multiple canvases which could massively decrease you database query load! Find out more here. |
The following video demonstrates how to make use of Count's local DuckDB database.