alamb commented on issue #348:
URL:
https://github.com/apache/arrow-datafusion/issues/348#issuecomment-1029436437
I ran the following to see where the time was going in my normal development
loop:
```
cargo +nightly test -p datafusion -Z timings
```
And the output was instructive. Specifically it seems to take 28.6 seconds
to compile the actual datafusion crate, but a whopping 65.6s to compile the
tests (aka `cfg(test)`). I'll keep plugging away at moving test code out of the
`datafusion` crate and into integration tests
```
Completed datafusion v6.0.0 in 28.6s
Completed datafusion v6.0.0 test "merge_fuzz" (test) in 4.6s
Completed datafusion v6.0.0 test "order_spill_fuzz" (test) in 4.7s
Completed datafusion v6.0.0 test "simplification" (test) in 4.8s
Completed datafusion v6.0.0 test "dataframe" (test) in 6.1s
Completed datafusion v6.0.0 test "provider_filter_pushdown" (test) in 6.7s
Completed datafusion v6.0.0 test "custom_sources" (test) in 6.7s
Completed datafusion v6.0.0 test "statistics" (test) in 6.8s
Completed datafusion v6.0.0 test "path_partition" (test) in 6.9s
Completed datafusion v6.0.0 test "user_defined_plan" (test) in 7.0s
Completed datafusion v6.0.0 test "dataframe_functions" (test) in 7.4s
Completed datafusion v6.0.0 test "parquet_pruning" (test) in 7.9s
Completed datafusion v6.0.0 test "sql_integration" (test) in 19.2s
Completed datafusion v6.0.0 lib (test) in 65.6s
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
