DuckDB on the server

When cells return a large results set, by default Count will only return the first 10,000 rows of the results to your browser. When this happens, the footer of the cell will contain some information about the full result set:

When partial results are returned, this information is displayed.

You can choose to download all of the results, in which case downstream Python and DuckDB cells will continue to run in your browser.

Otherwise, any downstream DuckDB cells will be executed on Count's servers rather than in your browser. When running on the server:

• The full results of any upstream cells are always available

• DuckDB may have access to more working memory than it does when running in a browser

• Queries may fail if they use too much memory, or attempt to access files on the local filesystem

The versions of DuckDB in your browser and on Count's servers are the same, so you shouldn't notice any difference when running queries.

When a DuckDB cell is running on Count's servers, the footer will show DuckDB (server).

You may also see DuckDB cells running on the server when your local DuckDB database is nearing its memory limit.