(NOT FOR MERGING) Print out the size of docker container after ARROW-12112

[alamb]

To answer a question #9879 (review) from @pitrou, I added some diagnostic information to the integration tests to see where the space is being taken up

This PR is based on master immediately AFTER to #9879

[github-actions]

Thanks for opening a pull request!

Could you open an issue for this pull request on JIRA?
https://issues.apache.org/jira/browse/ARROW

Then could you also rename pull request title in the following format?

ARROW-${JIRA_ID}: [${COMPONENT}] ${SUMMARY}

See also:

• Other pull requests
• Contribution Guidelines - How to contribute patches

[pitrou]

Ok, so before we had:

1.5G	/arrow/rust/target/debug/examples
6.4G	/arrow/rust/target/debug/deps
1.8G	/arrow/rust/target/debug/incremental
11G	/arrow/rust/target/debug
11G	/arrow/rust/target
11G	/arrow/rust

We now have:

977M	/arrow/rust/target/debug/examples
4.4G	/arrow/rust/target/debug/deps
1.3G	/arrow/rust/target/debug/incremental
7.1G	/arrow/rust/target/debug
7.1G	/arrow/rust/target
7.1G	/arrow/rust
7.5G	/arrow/

While we're making progress, this is still huge. By comparison, the C++ build takes 223 MB (that said, perhaps we should also count the conda environment: roughly 3.2 GB).

@alamb Would you like to open a JIRA to further try to reduce the Rust build size? Perhaps one direction would be to make the build more modular (the integration tests don't neet datafusion, parquet and other features, for example).

[alamb]

@alamb Would you like to open a JIRA to further try to reduce the Rust build size? Perhaps one direction would be to make the build more modular (the integration tests don't neet datafusion, parquet and other features, for example).

@pitrou -- good idea. I have filed https://issues.apache.org/jira/browse/ARROW-12204 / #9889 to reduce the integration test size

I will continue the investigation there