Skip to content
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

optimize binary size of RisingWave #15150

Open
BugenZhao opened this issue Feb 20, 2024 · 1 comment
Open

optimize binary size of RisingWave #15150

BugenZhao opened this issue Feb 20, 2024 · 1 comment
Labels
no-issue-activity type/enhancement Improvements to existing implementation.

Comments

@BugenZhao
Copy link
Member

The binary for x64 Linux of the recent release (v1.6.1) is 206 MB after compression, or 302 MB including the Java connector. Although RisingWave is primarily designed to be a server software where the binary size may not be critical, optimizing the binary size can enhance the experiences for users who use RisingWave in a lightweight manner.

As a contrast, here's a list of the compressed binary sizes of some other databases:

  • GreptimeDB, Rust, 61 MB
  • Databend, Rust, 299 MB
  • DuckDB, C++, 27 MB

Some portions that may contribute to the size:

  • (undoubtedly) libraries for integrating with external connectors
  • monophorization of the generic code
  • debug symbols section
@BugenZhao BugenZhao added the type/enhancement Improvements to existing implementation. label Feb 20, 2024
@github-actions github-actions bot added this to the release-1.7 milestone Feb 20, 2024
@BugenZhao BugenZhao modified the milestones: release-1.7, release-1.8 Mar 6, 2024
@BugenZhao BugenZhao removed this from the release-1.8 milestone Apr 8, 2024
Copy link
Contributor

This issue has been open for 60 days with no activity. Could you please update the status? Feel free to continue discussion or close as not planned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-issue-activity type/enhancement Improvements to existing implementation.
Projects
None yet
Development

No branches or pull requests

1 participant