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

investigate improving binary sizes #14

Closed
decathorpe opened this issue Sep 14, 2023 · 1 comment
Closed

investigate improving binary sizes #14

decathorpe opened this issue Sep 14, 2023 · 1 comment

Comments

@decathorpe
Copy link
Member

I am not sure what causes binaries (like simple client example binaries) to be as big as they are (multiple MB in release mode), but it might be due to monomorphization of some core functions.

Maybe things could be slightly improved using the "non-generic inner function" trick for some of these generic functions?

@decathorpe
Copy link
Member Author

With the updates to hyper 1 / reqwest 0.12 / axum 0.7 and some changes to the client interface, example binaries are now ~30% smaller. Not sure which change contributed how much to this improvement, but just ~2MB per application binary seems pretty good now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant