New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minified version with no table engines #53
Comments
I did some analysis with bloaty, the
Full table: clickhouse.sizeinfo.csv |
@alexey-milovidov any input or comments on this intent and related opportunities from the ClickHouse team? |
We can easily disable particular storages during the build - first try to do it manually and check the difference in the binary size. Then we can introduce some flags for it. Disabling functions is as easy as removing a .cpp file. Also, we can get benefits from the removal of the dynamic symbol table: ClickHouse/ClickHouse#47475 |
Simply strip can reduce about 100MB file size. |
@zhanglistar true, but we already strip libchdb.so which brings it to about ~380MB uncompressed and ~100MB compressed. |
Also, disabling some third party libraries can reduce size, like hive or mysql etc. |
Thanks, I have disabled unnecessary libs for chdb. Hive and MySQL might be useful for chDB users. |
@nmreadelf is working on that |
A lot of binary size comes from the tables engines that may not be relevant for in-process use cases like the merge tree engines, log engines, etc.
Would be great to either have an easy way to compile with engines omitted, or a build that is effectively engine-free (except for some basics like url, s3, file) for a far smaller build. The expectation is that custom engines would be made on top of the url/s3 engines in #52 as sorts of aliases
The text was updated successfully, but these errors were encountered: