[
https://issues.apache.org/jira/browse/ARROW-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646446#comment-16646446
]
Antoine Pitrou commented on ARROW-3491:
---------------------------------------
Running some timings here (Ubuntu 18.04, gcc 7.3.0), on the ARROW-3442 branch:
* cold debug build (ccache flushed) without split DWARF:
{code}
real 1m43,742s
user 11m4,532s
sys 0m46,878s
{code}
* cold debug build (ccache flushed) with split DWARF:
{code}
real 1m44,847s
user 11m17,830s
sys 0m48,983s
{code}
So there doesn't seem to be an improvement in full build time. As for the disk
footprint:
* without split DWARF:
{code}
$ du -h --max-depth=1 build-test/
272M build-test/debug
696K build-test/double-conversion_ep
27M build-test/double-conversion_ep-prefix
256K build-test/CMakeFiles
321M build-test/src
20K build-test/tools
24K build-test/examples
116M build-test/jemalloc_ep-prefix
737M build-test/
{code}
* with split DWARF:
{code}
$ du -h --max-depth=1 build-test/
198M build-test/debug
492K build-test/double-conversion_ep
27M build-test/double-conversion_ep-prefix
260K build-test/CMakeFiles
312M build-test/src
20K build-test/tools
24K build-test/examples
116M build-test/jemalloc_ep-prefix
654M build-test/
{code}
> [C++] Experiment with split DWARF
> ---------------------------------
>
> Key: ARROW-3491
> URL: https://issues.apache.org/jira/browse/ARROW-3491
> Project: Apache Arrow
> Issue Type: Wish
> Components: C++
> Reporter: Antoine Pitrou
> Priority: Minor
>
> From the article at
> http://www.productive-cpp.com/improving-cpp-builds-with-split-dwarf/, it
> should be possible to split debug information from .o files to have faster
> C++ builds and smaller disk footprint of libraries / executables. This is
> useful for development builds.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
