You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Daniel Becker (Jira)" <ji...@apache.org> on 2023/06/01 09:33:00 UTC
[jira] [Commented] (IMPALA-12175) Reduce debug info for bit-packing.cc to speed up compiling
[ https://issues.apache.org/jira/browse/IMPALA-12175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728283#comment-17728283 ]
Daniel Becker commented on IMPALA-12175:
----------------------------------------
It may be worth adding a comment about this in bit-packing.cc so if we do need to examine the variables we know why it doesn't work and how to proceed.
> Reduce debug info for bit-packing.cc to speed up compiling
> ----------------------------------------------------------
>
> Key: IMPALA-12175
> URL: https://issues.apache.org/jira/browse/IMPALA-12175
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 4.3.0
> Reporter: Joe McDonnell
> Priority: Major
>
> be/src/util/bit-packing.cc creates a large number of variants. The object file is enormous and takes a long time to assemble:
> {noformat}
> $ du -sh be/src/util/CMakeFiles/Util.dir/bit-packing.cc.o
> 223M be/src/util/CMakeFiles/Util.dir/bit-packing.cc.o{noformat}
> This is due to debug information. Setting -g1 for this file reduces the size dramatically:
> {noformat}
> $ du -sh be/src/util/CMakeFiles/Util.dir/bit-packing.cc.o
> 25M be/src/util/CMakeFiles/Util.dir/bit-packing.cc.o{noformat}
> I don't think this debug information is very useful for us, because we almost never step through or examine the variables for these functions. Limiting debug info to -g1 (which is enough for stack traces) might be worth it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org