4 ms·
Snaplet person here: Having a native WASM version would be a huge win for everyone, especially is storage is decoupled from compute! At the moment the CPU and
by pistoriusp 4y ago
Snaplet person here: Having a native WASM version would be a huge win for everyone, especially is storage is decoupled from compute!
At the moment the CPU and memory snapshot of the VM (with Postgres) is 12 MB, and subsequent reloads are cached. So yeah, not the worst, but not great.
An optimization is that we're using 9P filesystem. So accessing anything on disk is lazily loaded over the network.
> Are there future plans at creating a native WASM version of Postgres?
Yup! I think that should be the goal, and we (Supabase & Snaplet) would be very happy to work with anyone that wants to build towards that.
- chrisjc 4y ago> especially is storage is decoupled from compute! This would be amazing! I can imagine a situation where external tables are managed by some MPP, and a WASM compute engine (Postgres, DuckDB, etc) would be able to at least read subsets/partitions of the full external table. I wonder if the work required to make a native WASM Postgres would have to be split up into efforts for row-based vs column-based. Selfishly, I would love to have access to a column-based version first.
- pistoriusp 4y agoWe actually kinda see parts of this in https://github.com/superfly/litefs https://github.com/superfly/litefs, albeit for SQLite. And here we see some ideas forming around "pluggable storage for PostgresQL": https://wiki.postgresql.org/wiki/Future_of_storage#Pluggable_storage_for_tables https://wiki.postgresql.org/wiki/Future_of_storage#Pluggable... Seriously! If any of this sounds interesting to build, reach out, and we'll make it happen!