As others have mentioned it's a difficult test as some have native support for H3, but Mark has some great real-life benchmarks, I would prefer to see the load

As others have mentioned it's a difficult test as some have native support for H3, but Mark has some great real-life benchmarks, I would prefer to see the load times included in the total time as they can be significant. I think you can improve the BigQuery benchmark with a few simple tweaks similar to how you did on Postgres even using on-demand: - Use CTAS rather than altering (very slow on BQ) - Store the lat,lng as a Geography Point type on ingestion (increases performance significantly vs casting) - Consider spatially clustering the table around the H3 output (wont affect benchmark speed but will make subsequent processing speedy!)