pitrou opened a new issue, #36090: URL: https://github.com/apache/arrow/issues/36090
### Describe the bug, including details regarding any error messages, version, and platform. Here is a full debug build with Acero disabled (572 build steps), as of changeset 95972cca1f65179b63a9fe5262d1092547e3d137: ``` real 2m22,463s user 38m39,322s sys 2m26,218s ``` Here is the same build with Acero enabled (642 build steps): ``` real 2m39,304s user 45m11,410s sys 2m51,336s ``` So compiling Acero + tests is worth 7 minutes of CPU time, which seems a bit large. More generally, Arrow C++ compile times (in debug mode) seem to have increased by 25% - or 7 additional minutes of CPU time - between 11.0.0 and 12.0.0, which is not sustainable: * debug build on 11.0.0 (552 build steps): ``` real 2m17,473s user 37m37,749s sys 2m24,311s ``` * same debug build on 12.0.0 (634 build steps): ``` real 2m35,782s user 44m12,064s sys 2m48,723s ``` ### Measurements notes * `ccache` was disabled * CUDA, Dataset, Flight, Gandiva were disabled * Compute, GCS, Parquet, Orc, S3 were enabled * shared libraries only * using `ld.gold` * target build directory resides on a [zram](https://en.wikipedia.org/wiki/Zram) filesystem ### Component(s) C++ -- 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: issues-unsubscr...@arrow.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
