4 ms·
Sideline question: how do you end up with 2.5GB binary (ClickHouse as given in the readme)?
by alfanick 1y ago
Sideline question: how do you end up with 2.5GB binary (ClickHouse as given in the readme)?
- eclbg 1y agoClickHouse is a completely stand-alone binary that doesnt rely on any linked libraries. Not sure how much of this explains the large binary size, though.
- PhilipRoman 1y ago#include <iostream>
- deleted 1y ago[deleted]
- mmoskal 1y agoVery typical for anything with CUDA (they tend to compile everything for 10 different architectures times hundreds of template kernel parameters). Not sure about ClickHouse though.
- mrazomor 1y agoHeavy use of C++ templates can significantly increase the binary size. Same for the heavy use of generated code (e.g. protocol buffers etc.).
- zX41ZdbW 1y agoThis is visible in the embedded binary viewer: https://play.clickhouse.com/binary?user=binary&zoom=0&x=16203&y=14505 https://play.clickhouse.com/binary?user=binary&zoom=0&x=1620... (It shows only about 500 MB of machine code, and the rest of the gigabytes are debug info.)