Live data from Hacker News

DuckDB-Wasm: Efficient analytical SQL in the browser

duckdb.org

1–10 of 62 posts

Re: DuckDB-Wasm: Efficient analytical SQL in the browser

#3

Does DuckDB support multi tab usage? How big is the wasm file that must be loaded?

The WebAssembly module is 1.6 - 1.8 MB brotli-compressed depending on the Wasm feature set. We're currently investigating ways to reduce this to around 1 MB. We further use streaming instantiation which means that the WebAssembly module will be compiled while downloading it. But still, it will hurt a bit more than a 40KB library.

Regarding multi-tab usage: Not today. The available filesystem apis make it difficult to implement this right now. We're looking into ways to make DuckDB-Wasm persistent but we can only read in this release.

Re: DuckDB-Wasm: Efficient analytical SQL in the browser

#4

Does DuckDB support multi tab usage? How big is the wasm file that must be loaded?

On https://shell.duckdb.org/versus, we have a comparison with related libraries. The WASM bundles currently is 1.8 MB but it can be instantiated while it's streaming in.

The size probably makes it prohibitive to use DuckDB when your dataset is small and download size matters but we hope that future improvements in WebAssembly can get the size down.

Re: DuckDB-Wasm: Efficient analytical SQL in the browser

#6
I'm still not sure I "get" the use case for DuckDB. From what I understand, it's like a nifty, in-memory SQL, but why is that better than just running PostGRES or Microsoft SQL server locally, where your data structures and tables and stuff have a lot more permanence?

Like, my workflow is either I query an exiting remote corporate DB and do my initial data munging there, or get givne a data dump that I either work on directly in Pandas, or add to a local DB and do a little more cleaning there. Not at all clear how Duck DB would hel

Re: DuckDB-Wasm: Efficient analytical SQL in the browser

#7

I'm still not sure I "get" the use case for DuckDB. From what I understand, it's like a nifty, in-memory SQL, but why is that better than just running PostGRES or Microsoft SQL server locally, where your data structures and tables and stuff have a lot more permanence? Like, my workflow is either I query an exiting remote corporate DB and do my initial data munging there, or get givne a data dump that I either work on…

Not just in-memory. It's pretty convenient if you have a set of Parquet files with common schema. Fairly snappy and doesn't have to fit in memory.

Re: DuckDB-Wasm: Efficient analytical SQL in the browser

#8

I'm still not sure I "get" the use case for DuckDB. From what I understand, it's like a nifty, in-memory SQL, but why is that better than just running PostGRES or Microsoft SQL server locally, where your data structures and tables and stuff have a lot more permanence? Like, my workflow is either I query an exiting remote corporate DB and do my initial data munging there, or get givne a data dump that I either work on…

I don't fully get the use case either, but it's in a different category than Postgres or Microsoft SQL because it runs in the browser and can be made part of your web app.
Post reply on HN