Indeed, it would have been interesting but I really wanted to get the blog post out on the launch day of the MacBook Neo and did not have the bandwidth to run a

Indeed, it would have been interesting but I really wanted to get the blog post out on the launch day of the MacBook Neo and did not have the bandwidth to run additional cloud experiments. I ran TPC-DS SF300 now on the c6a.4xlarge. It turns out that it's still quite limited by the EBS disk's IO: while 32 GB memory is much more than 8 GB, DuckDB needs to spill to disk a lot and this shows on the runtimes. Running all 99 queries took 37 minutes, so about half of the MacBook's 79 minutes. > Command being timed: "duckdb tpcds-sf300.db -f bench.sql" > Percent of CPU this job got: 250% > Elapsed (wall clock) time (h:mm:ss or m:ss): 37:00.96 > Maximum resident set size (kbytes): 25559652