Interesting result. With Unity Catalog OSS we are now able to create local Lakehouse (in one word, as Lake House refer to the AWS S3 + Redshift or DL + DWH architecture).
Hi, I read this article and I am surprised that DuckDB is slow in AWS.
My question is: is the problem is in AWS(cloud) or in DuckDB? Have you tried other cloud to see the results? In my opinion AWS is the problem. Untill unless DuckDB is designed for a dedicated cloud.
Surprising. Rust is really good at asynchronous network calls, maybe that makes a difference.
Interesting result. With Unity Catalog OSS we are now able to create local Lakehouse (in one word, as Lake House refer to the AWS S3 + Redshift or DL + DWH architecture).
Hi, I read this article and I am surprised that DuckDB is slow in AWS.
My question is: is the problem is in AWS(cloud) or in DuckDB? Have you tried other cloud to see the results? In my opinion AWS is the problem. Untill unless DuckDB is designed for a dedicated cloud.
daft probably downloaded data from the cache?