Observable Framework 1.13.0 duckdb wasm size.

[petermerrick87]

I recently updated our observable framework app to 1.13.0 to get access to duckdb extensions, namely the spatial extension for some deckgl mapping. We have observable running inside of cloud run, and cloud run has a hard limit of 32mb for each file served.

Previously (1.12.0) the download was about 18mb.

Now (1.13.0) downloading duckdb-wasm looks like this, 36mb.

This causes duckdb to be blocked, and the app to cease to work.

@Fil notes here #1734 that he also sees the package size doubling, similar to what I am seeing, however mentions base download sizes much smaller than what I note in the browser.

But it's still doubling the (compressed) size of the base files from 4MB to ~8MB (depending on the extensions needed… here I compare 1.28.0 with 1.29.0+parquet)

Are duckdb wasm files expected to exceed 32mb transferred to the client? If so I will have to think about how we will host the app going forward.

[petermerrick87]

Sorted this one today, our environment was not using any compression, which caused the difference between Fils observations and ours. Our duckdb package is now around the 8mb size and serves fine from Cloud Run.