While reviewing recent DataFusion results, I found there is now a "load time" reported for DataFusion
For example, this link
Here is the source file that has 17:
It was added in 6d5ee0a which was part of a large refactoring in #860
I am not sure if you intended the load_time to include the download / fsync time for the raw parquet dataset, but if you did I would request that we measure it consistently across stateless engines
While reviewing recent DataFusion results, I found there is now a "load time" reported for DataFusion
For example, this link
Here is the source file that has 17:
ClickBench/datafusion-partitioned/results/20260511/c6a.4xlarge.json
Line 10 in a377499
It was added in 6d5ee0a which was part of a large refactoring in #860
I am not sure if you intended the load_time to include the download / fsync time for the raw parquet dataset, but if you did I would request that we measure it consistently across stateless engines