-
-
Notifications
You must be signed in to change notification settings - Fork 135
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
[reduce size] Very large resulting library file for compute1
crate
#386
Comments
compute1
crate
compute1
cratecompute1
crate
For the Unfortunately it looks like a regression snuck in to the CLI generator with this (and 2 more errors just like it):
Probably the CLI generator doesn't yet know about the improved types that were recently introduced, and I'd love it if that could be fixed. From there it should be possible to get values for release binaries that make use of every possible call, i.e. the worst case scenario. |
It looks like the upgrade to |
The debug build of compute3-cli is 108MB (MacOS) and 52MB stripped. The release build is still… running 😅 (4.2GB in memory). |
42 minutes later, there was a release binary of |
Updating crates.io index Compiling google-compute1 v5.0.1+20220224 (/.../google-apis-rs/gen/compute1) Finished dev [unoptimized + debuginfo] target(s) in 43.67s
This produces a 181MB (debug) / 168MB (release) library file.
This issue is intended to track progress over time - ideally, this library should be a good bit smaller.
The text was updated successfully, but these errors were encountered: