-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
size of librocksdb.a is too huge #12636
Comments
by the way, when will the v9.2 release ready? |
Hi @979357361 , have you tried stripping the
So running the |
Hi @jsteemann, thanks for your time. In my build, after [strip], compile will error with [undefined reference to xxxx (C API)], but the compile do work before strip, so is there something wrong? another thing bothering me is that, [INSTALL.md] tell me that RocksDB's library should be able to compile without any dependency installed. I do not use compress in ROCKSDB, so there is n0 libzstd in my server, if I use [make -j static_lib] to build librocksdb.a, it works and I can compile my program and run it, but for librocksdb.so with cmd [make -j shared_lib], it goes wrong with "cannot find -lzstd", it seems unreasonable? CC utilities/transactions/lock/range/range_tree/range_tree_lock_tracker.o |
@979357361 : I can't say much about building the shared library, because I never tried to do so myself. In case you are wondering how large the sections in the library file are, you can try Google Bloaty to analyze the library file. In my case, it prints
But your mileage may vary. |
Hello guys, good day! I am here for help again...
I want to use rocksdb in my C program, and I prefer to static link.
I use <make -j static_lib> to compile the static lib, as a result I get a librocksdb.a file whose size is more than 1GB, this is too heavy, after link rocksdb, my program size goes to 300MB+ from 30MB, this seems unacceptable.
Could you please tell me how to slim the librocksdb.a? to be more exact, what could I do to slim my program?
thanks for your time, good day again~
The text was updated successfully, but these errors were encountered: