-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Investigate the size of the binary #1060
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
Comments
Does anyone have good resources / online manuals on how to investigate code size? |
I know of |
https://github.com/johnthagen/min-sized-rust |
Okay, I did some measurements. rustpython commit: 9e194b3 First build in release mode:
Enable LTO (link time optimization) in Cargo.toml
Run strip on the lto build:
|
Oh wow, that's a lot better! |
Probably this issue can be closed now ;) @windelbouwman |
For now,
|
The size is still too large for our use case, I suppose we can continue the discussion in this issue: #4203 |
Our builds are rather large at this point. The release build is 18MB, the debug build is 89MB. This is rather big, and slows things down. What is the cause of this code size?
The text was updated successfully, but these errors were encountered: