[C++] arrow_reader_writer_test.cc slow to compile
- Dominant language
- C++
- Stars
- 17.1k
- Forks
- 4.3k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 88
Description
As soon as some optimizations are enabled, `src/parquet/arrow/arrow_reader_writer_test.cc` becomes extremely slow to compile (more than one minute just for itself). This is perceivable on e.g. the `conda-cpp-valgrind` build where we add `-Og` to the gcc flags in order to make the tests less slow under emulation.
**Reporter**: [Antoine Pitrou](https://issues.apache.org/jira/browse/ARROW-13221) / @pitrou
**Note**: *This issue was originally created as [ARROW-13221](https://issues.apache.org/jira/browse/ARROW-13221). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
Contributor guide
Research direction
Start by compiling src/parquet/arrow/arrow_reader_writer_test.cc in the conda-cpp-valgrind build with -Og and compare its compile time. Read the test structure and identify what makes this translation unit slow to compile; done means the test compiles substantially faster without losing its coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- performance, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100