// writing · data lakes and query engines
Data lakes and query engines
Register Iceberg tables in a Postgres catalog for faster Trino queries
A small Postgres database, two tables and one row per Iceberg table took my Trino lookups from 13 seconds to under one.
Data lakes and query enginesTrino vs StarRocks vs Doris on an Azure Iceberg lake
Same tables, same machine, same six questions. One engine was fastest, one was most familiar, and one couldn’t read the files at all.
Data lakes and query enginesMaking a Trino lake as fast as a SQL database
Most of the slowness wasn’t the engine. It was the questions the engine asked before it started.
Data lakes and query enginesThe small file problem, measured on disk and in Azure
Same 2 million rows, same answer. What changed, what compaction fixed, what VACUUM quietly broke, and what it looks like from Azure.
Data lakes and query enginesAn open table format is only as open as the tool that wrote it
I saved the same table as Delta and Iceberg. The format was never what made them differ.
Data lakes and query engines